1. Authorised contact
Identify the person who can approve the investigation, sign engagement documents and make decisions for the organisation.
Understand how a security engagement works, what authorisation is required, what information to prepare and what to expect before technical work begins. We can provide the relevant forms and checklists when you request a service.
Please review these important points before sharing details of a suspected incident.
Each investigation is different. The exact documents and information required depend on the service, systems involved and agreed scope.
We first establish what may have happened, whether the incident is ongoing, which systems or accounts may be affected and who is authorised to instruct us. We then recommend an appropriate next step and define the proposed scope, deliverables, timing and fees before investigation work begins.
Yes. You do not need to diagnose the incident before contacting us. Tell us what you observed, when it started, which users or systems are affected and whether business operations are disrupted. We can help determine whether initial triage or a more detailed investigation is appropriate.
No. Subject to availability, authorisation, technical access and acceptance of the engagement scope, services may be requested by existing clients or on a once-off basis. An existing managed IT agreement does not automatically include forensic investigations, incident remediation or unlimited response work.
We assess urgency and availability when you contact us. Any response target depends on the service or SLA agreed with us. A response target means acknowledgement and initial triage, not a promise that the incident will be contained or resolved within that time.
Investigations may involve accessing devices, accounts, networks, logs or personal information. Written authorisation confirms that the person instructing us has authority to request the work and identifies what we are permitted to access or test. We do not begin access, scanning, penetration testing or evidence collection without appropriate documented authority.
You must have the right to authorise the requested activity. If systems, applications, hosting, networks or data are controlled by another organisation, we may require written permission from the relevant owner or provider. Your own authorisation does not automatically grant permission to test someone else’s environment.
The scope records systems, users, devices, IP addresses, locations, data volumes, investigation period, permitted activities, engineering hours, deliverables and exclusions. Work outside those limits is not automatically included and may require a revised quotation or change approval.
Yes, where offered and accepted as a specifically authorised engagement. Before testing, we agree target assets, test window, techniques permitted, exclusions, emergency contacts and stop conditions. We do not test third-party systems or expand testing beyond the approved scope.
Depending on the incident, we may ask for your organisation name, authorised contact, a short description of what happened and when, affected systems or users, operational impact, relevant IT contacts, actions already taken and available alerts or logs. If you do not know an answer, say so. Do not guess or delay contacting us.
We may need to identify relevant user accounts, roles or systems. Any access required must be agreed in advance and provided using an approved, secure method with appropriate permissions. Do not send passwords, MFA codes, recovery keys or private keys in a website form, chat message or ordinary email.
Tell us what is unavailable and who manages the relevant system. We can assess alternative evidence sources and may help identify what should be requested from your IT provider, cloud provider, internet service provider or software vendor. Findings may be limited if relevant logs or evidence are unavailable, incomplete or expired.
Yes. When you request a service, ask us for the relevant client documentation. Depending on the engagement, we can supply an incident intake checklist, client authorisation form, scope-of-work document, evidence handover checklist and other relevant engagement documents. We will identify which documents apply rather than expecting you to prepare everything yourself.
Do not automatically power off, reboot, wipe or reinstall a suspected compromised device. Those actions may destroy volatile information or alter evidence. If safe and practical, isolate an affected device from networks while leaving it powered on, and contact us for incident-specific guidance. If there is an immediate safety or operational risk, follow your organisation’s emergency procedures.
Logs, timestamps, files, system state and other records may help establish what happened and when. Unplanned changes can overwrite or alter useful evidence. We discuss preservation requirements and any agreed acquisition or handling process before performing work that could affect evidence.
Information access should be limited to what is reasonably necessary for the agreed service and handled under applicable contractual and legal obligations. We agree suitable transfer, access, retention and disposal arrangements for sensitive material. Specific controls and documentation depend on the engagement.
Personal information involved in an engagement must be handled in accordance with applicable data-protection obligations, including POPIA where applicable. The parties should establish their respective roles, purposes, instructions, safeguards, retention requirements and any cross-border considerations in the engagement documents. This FAQ is general service information, not legal advice.
Not every technical investigation is a formal forensic examination or expert report. If evidence may be used in disciplinary, regulatory, civil or criminal proceedings, tell us before work begins. We can discuss methodology, documentation, chain-of-custody, independent expert involvement and whether the requested service is suitable. Legal advice and expert testimony are not automatically included.
Investigation effort depends on the number of affected devices, servers, users, mailboxes, evidence sources, data volume and complexity. Packages specify included quantities and engineering hours so that a starting fee does not imply an unlimited environment.
We explain what is outside the original scope and provide the additional cost or revised quotation. Work beyond the agreed devices, users, data volume, hours or locations proceeds only after the client approves the additional scope in writing.
No. An initial assessment is limited to the stated assets and hours and focuses on understanding the incident and recommending next steps. Containment, malware removal, forensic acquisition, rebuilds, backup restoration and recovery are separate activities unless expressly included in the signed quotation.
No. Decryption and recovery depend on factors such as the ransomware variant, available keys, damage, backups and system condition. We cannot guarantee encrypted data can be decrypted or recovered. We assess available options and explain risks and practical next steps.
Not unless the quotation says so. On-site attendance, travel distance, travel time, parking, tolls and accommodation may be charged separately. The applicable travel estimate and charges are confirmed before dispatch. Remote work does not attract travel charges.
Response time is the target for acknowledging the report and beginning initial triage under the agreed SLA. Resolution time is how long it takes to contain, investigate, remediate or restore the affected environment. Resolution depends on incident complexity, client decisions, access, third parties and available backups; it is not guaranteed by the response target.
You do not need to have every item ready before contacting us. This checklist helps the engagement move forward once we have established the incident and agreed the scope.
Identify the person who can approve the investigation, sign engagement documents and make decisions for the organisation.
Record what was noticed, when it began, what messages or alerts appeared and whether the issue is continuing.
List known affected endpoints, servers, users, mailboxes, applications, sites and service providers. Estimates are acceptable initially.
Tell us about devices isolated, accounts disabled, passwords reset, systems rebooted, files deleted or backups restored.
Identify where relevant logs, alerts, backups or screenshots may exist. Do not alter, clean up or send sensitive evidence before agreeing a safe method.
Identify the internal IT administrator or third-party provider who can assist with approved access and information requests.
Explain which business operations are affected, whether critical services are unavailable and any immediate operational deadlines.
Ask us for the applicable authorisation, incident intake, scope-of-work and evidence handling documents. We will supply the relevant pack for your engagement.
Clear steps. Controlled access. Agreed scope.
Share a high-level description without sending passwords or sensitive evidence.
We identify the authorised representative and provide the relevant client documents.
We agree affected assets, limits, deliverables, fees, access and evidence requirements.
Work starts within the agreed scope, with additional work approved before it proceeds.
The final engagement documents and signed quotation or SLA take precedence over this general FAQ if there is any difference in wording or scope.
Contact us and tell us which service you are considering. We can supply the applicable authorisation form, incident intake checklist, scope document and evidence handling checklist where required.
Request client documents →