Start with the decision you need to make, the type of system or artefact involved, and the boundary of the proposed work. Detailed technical material is handled only after fit and authority are confirmed.
Prepare a useful assessment request
The first message should help route the enquiry without exposing the material that may later need protection.
Name the decision
Explain whether you need to understand, validate, strengthen, respond, recover or obtain assurance.
Describe the boundary
Name the general system, application, artefact or environment without attaching it.
State authority
Confirm that you own the target or are authorised to commission the proposed work.
Keep evidence private
Do not paste code, credentials, logs, malware, client records or classified details.
Active incident?
Use Get incident help instead. That route asks for less detail and prioritises safe first actions.
Planned work
Request a scoped assessment
Tell us the decision and boundary, not the evidence.What happens after submission
Acknowledge
An automatic email confirms that the request entered the delivery path.
Review fit
The team checks the service, authority, sensitivity and requested outcome.
Clarify scope
Any detailed questions or private transfer needs move to an appropriate channel.
Agree work
A signed agreement and verified scope are required before analysis or testing begins.
Submissions are delivered to team@malwareanalysis.app. The contracting entity is Cybersecurity Engineering Pty Ltd (ABN 45 702 088 533).