CyberAdvisor℠ Overview
CyberAdvisor℠ · 24/7 Digital Forensics & Incident Response

Cyber incident? Know these 10 things before you call.

Call 24/7(973) 298-1160

Active incident? Do not wait for all 10 answers. Call now.

  • Ransomware
  • Business Email Compromise
  • Unauthorized Access
  • Data Theft
  • Malware
  • Insider Activity

When a cybersecurity incident happens, the first few hours matter.

Proactive Risk Digital Forensics & Incident Response (DFIR) helps organizations investigate, contain, document, and recover from cybersecurity incidents.

Need immediate assistance?

Call Proactive Risk 24/7. If the attack is happening right now, do not wait until you have answers to all 10 questions. Call us immediately.

1. What happened?

Tell us what you know.

Examples
  • Ransomware message appeared
  • Microsoft 365 account was compromised
  • Employee clicked a phishing email
  • Suspicious login was detected
  • Money was fraudulently transferred
  • Malware was discovered
  • Files were accessed or stolen
  • Laptop or device was lost
  • Third party notified you of a breach

Don't worry about diagnosing the incident yourself.

Tell us what you observed and let our incident responders investigate the cause.

2. When did you discover it?

Be prepared to provide:

  • Date and approximate time discovered
  • Who discovered the incident
  • What triggered the discovery
  • When you believe the incident may have started
  • How long suspicious activity may have occurred

The incident discovery date and actual compromise date may not be the same.

Establishing an accurate timeline is one of the first objectives of an incident-response investigation.

3. Is the attack still happening?

Tell us whether:

  • Accounts are still being accessed
  • Ransomware is still spreading
  • Systems remain unavailable
  • Suspicious logins continue
  • Malware remains active
  • Data may still be leaving the environment
  • Attackers may still have access

An active compromise may require immediate containment before the broader forensic investigation begins.

If you believe the attacker is still inside your environment, call Proactive Risk immediately.

4. What systems or accounts may be affected?

Create a quick list of potentially affected technology.

Examples include
  • Microsoft 365
  • Microsoft Entra ID
  • Email accounts
  • Windows computers
  • macOS computers
  • Servers
  • Firewalls
  • VPNs
  • Cloud infrastructure
  • SharePoint
  • OneDrive
  • SaaS applications
  • Websites
  • Backup systems
  • Network infrastructure

Even an approximate number helps us establish the initial investigation scope.

An investigation involving one compromised Microsoft 365 account is very different from an incident involving 100 endpoints, multiple servers, domain administrator credentials, and possible data exfiltration.

5. What information may have been exposed?

Consider whether affected systems contained:

  • Names and addresses
  • Social Security numbers
  • Driver's license or state identification information
  • Financial account information
  • Credit or debit card information
  • Usernames and passwords
  • Employee records
  • Customer records
  • Protected Health Information (PHI)
  • Personally Identifiable Information (PII)
  • Intellectual property
  • Confidential company information

It is important to distinguish between data that may have been:

  1. Accessed
  2. Acquired
  3. Exfiltrated
  4. Published

Unauthorized access does not automatically mean that information was stolen.

Determining what the attacker actually accessed or removed may become an important part of the forensic investigation.

6. Approximately how many people could be affected?

We initially need an estimate, not necessarily an exact number.

Consider
  • Employees
  • Customers
  • Vendors
  • Patients
  • Students
  • Members
  • New Jersey residents
  • Residents of other states

The scope of an investigation can change significantly between an incident involving one employee account and an incident potentially affecting thousands of individuals.

If personal information may be involved, determining the number and residency of potentially affected individuals may also become important for legal and regulatory analysis.

7. What evidence is available?

Do not intentionally delete potential evidence.

Evidence may include
  • Microsoft 365 audit logs
  • Microsoft Entra ID sign-in logs
  • Microsoft Defender telemetry
  • Firewall logs
  • VPN logs
  • Endpoint Detection and Response (EDR) telemetry
  • Windows event logs
  • Email headers
  • Suspicious emails
  • Malware
  • Ransom notes
  • Screenshots
  • Server logs
  • Cloud audit logs
  • SIEM alerts
  • Backup logs
  • Disk images
  • Memory captures

Preserving this information can help investigators determine what happened, when it happened, how the attacker gained access, and what the attacker did after gaining access.

8. What has already been done?

Tell us exactly what happened after the incident was discovered.

For example
  • Passwords were changed
  • Accounts were disabled
  • MFA was reset
  • Active sessions were revoked
  • Computers were disconnected
  • Firewall rules were changed
  • IP addresses were blocked
  • Systems were rebooted
  • Computers were reimaged
  • Backups were restored
  • Security scans were performed
  • Email forwarding rules were removed
  • OAuth applications were revoked

Do not hide mistakes or unexpected changes.

Knowing exactly what was done helps investigators understand what evidence may still be available.

9. Who has already been contacted?

Tell us whether you have notified or engaged:

Internal

  • Executive management
  • IT department
  • Security team
  • Legal counsel
  • Privacy officer
  • Compliance personnel

External

  • Cyber insurance carrier
  • Insurance breach coach
  • Outside legal/privacy counsel
  • Another incident-response provider
  • Local law enforcement
  • New Jersey authorities
  • FBI
  • CISA
  • Customers
  • Employees
  • Regulators

Knowing who is already involved helps establish communication responsibilities, reporting requirements, and the appropriate investigation workflow.

10. What do you need help with?

You don't need to know exactly which forensic services you need. Start by telling us the business problem.

"We think someone accessed our Microsoft 365 environment."
"Our files are encrypted and there's a ransom note."
"We think employee information was stolen."
"Someone transferred money after receiving a fraudulent email."
"We discovered an administrator account being accessed from another country."
"Our cyber insurance company told us we need an incident-response firm."

Proactive Risk will use the available information to establish the appropriate incident-response scope.

Stop: protect the evidence

If possible, speak with an incident responder before taking destructive remediation actions.

Unless immediate safety or business circumstances require otherwise, avoid unnecessarily:

  • Reimaging affected computers
  • Deleting suspicious files
  • Clearing logs
  • Factory-resetting devices
  • Deleting compromised accounts
  • Destroying suspicious emails
  • Removing affected systems without documenting them
  • Making widespread configuration changes without recording them

Start an incident log

Document:

WHO did WHAT to WHICH SYSTEM and WHEN.

2:14 PMJohn Smith disabled the affected Microsoft 365 account.
2:21 PMIT disconnected WS-104 from the network.
2:37 PMFirewall blocked suspected malicious IP address.

Evidence preservation can be important for:

  • Digital forensics
  • Cyber insurance
  • Legal review
  • Regulatory reporting
  • Litigation
  • Law-enforcement investigations
  • Root-cause analysis
What happens when you call

Our initial incident response focuses on four objectives.

  1. 01

    Contain

    Is the threat still active, and what needs to be isolated immediately?

    The priority is preventing additional damage while preserving evidence whenever practical.

  2. 02

    Investigate

    What happened, how did it happen, and what did the attacker do?

    We work to establish the incident timeline and investigate available forensic evidence.

  3. 03

    Scope

    Which systems, identities, information, and business processes were potentially affected?

    Establishing scope helps guide remediation, recovery, legal review, insurance coordination, and potential notification requirements.

  4. 04

    Recover

    What needs to happen to safely restore operations and reduce the likelihood of recurrence?

    Recovery may include credential resets, hardening, configuration changes, system restoration, monitoring, and remediation recommendations.

Capabilities

Digital Forensics & Incident Response services

Depending on the incident, Proactive Risk may provide:

  • Emergency incident triage
  • Incident containment
  • Microsoft 365 compromise investigation
  • Microsoft Entra ID investigation
  • Endpoint forensics
  • Compromise assessment
  • Log analysis
  • Evidence preservation
  • Business Email Compromise investigation
  • Ransomware investigation
  • Malware investigation
  • IOC identification and threat hunting
  • Data-exfiltration analysis
  • Root-cause analysis
  • Recovery guidance
  • Incident documentation
  • Executive incident reporting
  • Remediation recommendations
  • Cyber insurance coordination support
  • Legal counsel support
  • Law-enforcement coordination support
New Jersey

New Jersey cyber incident & data breach reporting

For organizations operating in New Jersey, a cybersecurity incident and a legally reportable data breach are not necessarily the same thing.

New Jersey maintains mechanisms for reporting cybersecurity incidents and data breaches to appropriate state authorities.

The technical investigation performed following an incident can help establish facts that management and qualified legal/privacy counsel may use to determine applicable notification requirements.

Important notice: Proactive Risk does not provide legal advice.

Organizations should work with qualified legal/privacy counsel to determine whether an incident constitutes a legally reportable breach and which federal, state, contractual, insurance, or industry notification requirements apply.

Don't wait for all 10 answers

These questions help us respond faster. They are not prerequisites for calling.

If you believe:

  • An attacker currently has access to your environment
  • Ransomware is spreading
  • Accounts are actively being compromised
  • Money is being fraudulently transferred
  • Sensitive information is actively being exposed
  • Critical systems are unavailable
  • A cyberattack threatens business operations

Call immediately.

24/7 Cyber Incident Response

Call Proactive Risk

Call 24/7(973) 298-1160

When you call, start with three things:

  1. 1.What happened
  2. 2.When you discovered it
  3. 3.Whether it is still happening

We'll take it from there.

Proactive Risk Digital Forensics & Incident Response

CONTAIN. INVESTIGATE. SCOPE. RECOVER.