EMERGENCY PROTOCOL // MODULE 05
⏱️ ESTIMATED TIME: 15 MINS

Incident Response, Account Compromise & Containment Triage

When an enterprise account is compromised, the first 60 minutes dictate whether an incident becomes a minor containment event or a catastrophic breach. Learn to identify subtle compromise indicators, execute session revocation, isolate endpoints, and preserve volatile RAM forensics.

1 CURRICULUM LESSONS
➔
2 INCIDENT SIMULATOR
➔
3 ASSESSMENT (80% TO PASS)
➔
4 OFFICIAL CERTIFICATE
SECTION 01 // TELEMETRY 🕵️

Recognizing Signs of Account Compromise

Overview: Cyber breaches rarely announce themselves with blaring ransomware notes immediately; they begin quietly. Detecting subtle, early anomalies halts lateral movement and limits operational blast radius before privilege escalation occurs.

Key Compromise Indicators:

  • Unauthorized Inbox Rules: Stealth forwarding rules that divert invoices, billing updates, or security notifications directly into obscure folders (e.g., RSS Feeds, Archive, or Trash).
  • Anomaly Logins: Concurrent authentications from distant geographical regions within physically impossible timeframes ("Impossible Travel"), or unexpected user-agent browser strings.
  • Security Configuration Tampering: Unsolicited registration of secondary MFA hardware keys, authenticator apps, or altered recovery email addresses.
🛡️ Key Defense Protocol

Treat any unexpected inbox rule or unfamiliar MFA device as an active security breach. Immediately alert SecOps rather than simply deleting the rule.

SECTION 02 // CONTAINMENT ⏱️

The "First 60 Minutes" Emergency Triage SOP

Overview: A structured, ordered response halts the attacker's persistent session cookies and prevents secondary access attempts.

Immediate 4-Step Triage Execution:

  • Immediate Step 1 — Session Invalidation: Terminate all active browser sessions, revoke OAuth application authorizations, and invalidate active refresh tokens across cloud identity providers (Microsoft 365, Google Workspace, Okta).
  • Immediate Step 2 — Credential Reset: Update primary passwords only AFTER terminating external sessions and removing unauthorized MFA devices.
  • Immediate Step 3 — Mailbox & Delegation Audit: Inspect inbox forwarding rules, delegator access lists, transport rules, and automatic reply filters.
  • Immediate Step 4 — Endpoint Isolation: Disconnect suspected physical or virtual endpoints from Wi-Fi and Ethernet without powering down the machine to preserve volatile RAM forensics.
🛡️ Key Defense Protocol

Never power off a compromised endpoint. Powering down permanently destroys volatile memory (RAM) where running malware processes, unencrypted keys, and active network connections reside.

SECTION 03 // FRAUD PREVENTION 💼

Mitigating Business Email Compromise (BEC)

Overview: Business Email Compromise (BEC) syndicates rarely deploy malware right away. Instead, they dwell silently in executive or accounting mailboxes, monitoring invoice threads until payment details are ready to exchange.

Attack Playbook & Interception:

  • Adversaries inject altered bank account details via PDF invoices right before wire execution.
  • They create mail rules to delete legitimate payment inquiries from real vendors.
  • They fabricate internal "executive approvals" citing time-sensitive confidential audits.
🛡️ Key Defense Protocol

Mandatory Out-of-Band Callback Verification: Any update to wire routing coordinates or beneficiary accounts requires verbal phone verification using pre-vetted numbers from internal master records—never numbers listed on the new invoice or email.

SECTION 04 // FORENSICS & COMMS 🔒

Evidence Preservation & Safe Reporting

Overview: Proper incident coordination ensures evidence remains legally defensible while preventing attackers from discovering that defenders have begun remediation.

Operational Reporting Protocols:

  • Log Integrity: Export sign-in logs, cloud audit logs, and raw RFC 822 email message headers prior to modifying compromised infrastructure.
  • Out-of-Band Emergency Channels: Never coordinate response activities via the suspected compromised email system (the attacker may be actively reading your emails). Use dedicated out-of-band bridges or encrypted channels.
  • Internal vs External Communication: Escalate strictly to the designated Incident Response Lead and SecOps triage team following Cyvexis breach reporting guidelines.
🛡️ Key Defense Protocol

Avoid Tipping Off Adversaries: Coordinating response within compromised email threads prompts attackers to deploy ransomware or purge forensic traces immediately.

CYVEXIS INCIDENT LABS // TACTICAL TRIAGE SIMULATOR

Interactive Incident Response Terminal

Inspect active compromise indicators, dissect stealth inbox rules, simulate session revocations, and review emergency containment workflows.

EXCHANGE ONLINE // INBOX RULE AUDIT ⚠️ 1 MALICIOUS RULE ACTIVE
🚨 ATTACKER BACKDOOR RULE DETECTED
IF Subject contains ['Invoice', 'Wire', 'Payment', 'Security', 'Password']
THEN MarkAsRead = True
AND MoveToFolder = 'RSS Feeds'
AND ForwardTo = 'finance-triage@adversary-exfil.xyz'
AND DeleteFromInbox = True

Forensic Analysis: The attacker configured this rule to suppress invoice notifications from real vendors and exfiltrate billing records to an external domain while hiding the emails in the unused RSS Feeds folder.

Cloud Identity Sign-In Telemetry

Identity Protection flagged two concurrent active sessions for sarah.chen@cyvexis.internal within an impossible physical transit window:

SESSION 01 // LEGITIMATE WORKSTATION

Location: New York, NY (USA)
Timestamp: 14:10:22 UTC
IP Address: 192.0.2.14
Client: Chrome 122 / macOS 14
Auth Method: FIDO2 Passkey ✓

SESSION 02 // IMPOSSIBLE TRAVEL ANOMALY

Location: Lagos, Nigeria
Timestamp: 14:22:45 UTC (+12 mins)
IP Address: 198.51.100.89
Client: Python-Requests / Linux
Risk Score: CRITICAL (Impossible Travel)

First 60 Minutes Triage Checklist

Execute these ordered response stages to contain account compromise before privilege escalation:

STAGE 01
Session Invalidation
Revoke all active browser sessions, OAuth permissions, and refresh tokens across cloud identity providers.
STAGE 02
Credential Reset
Purge unauthorized MFA devices, then reset master credentials to lock out the adversary.
STAGE 03
Mailbox Audit
Examine hidden inbox forwarding rules, delegator access permissions, and automated transport rules.
STAGE 04
Network Isolation
Unplug Ethernet & disconnect Wi-Fi. Do not power down the workstation to preserve volatile RAM.

Out-of-Band (OOB) Incident Communications

When an account or tenant is compromised, never coordinate incident response over internal email.

⚠️ CRITICAL OPERATIONAL WARNING:

If the adversary possesses global tenant observation privileges or has compromised an executive mailbox, discussing containment in that channel tips them off, allowing them to delete event logs or accelerate ransomware deployment.

KNOWLEDGE EVALUATION

Module 05 Threat Containment Assessment

Score: 0 / 6 Resolved
⚡ PASSING CRITERIA NOTICE
You must score at least 80% (minimum 5 out of 6 correct) to qualify for your official verified Cyvexis defense certificate. Review questions carefully before submitting.
QUESTION 01 // STEALTH INBOX RULES PENDING

An employee notices that client emails containing invoices are automatically bypassing their inbox and moving directly into the RSS Feeds folder. What is the most likely cause?

QUESTION 02 // IMMEDIATE INCIDENT ACTION PENDING

What is the very first action an administrator should take upon confirming an active account compromise?

QUESTION 03 // VOLATILE RAM FORENSICS PENDING

When isolating a suspected malware-infected workstation during an incident, why should you disconnect network cables rather than powering down the computer?

QUESTION 04 // VENDOR FRAUD & BEC INTERCEPTION PENDING

A finance manager receives an email from an established supplier requesting urgent payment updates to a new bank account due to an 'audit freeze'. What is the mandatory verification protocol?

QUESTION 05 // IMPOSSIBLE TRAVEL ANOMALY PENDING

What does an 'Impossible Travel' alert in cloud identity logs indicate?

QUESTION 06 // SAFE REPORTING CHANNELS PENDING

Why is it dangerous to coordinate incident response activities using the compromised organization's primary corporate email?

🔒 CERTIFICATE LOCKED - MINIMUM 80% (5/6) REQUIRED

Claim Your Module 05 Defense Credential

Complete all 6 threat evaluation questions above with at least 80% (5/6) correct to unlock your official verified certificate.

⚠️ Complete all 6 threat evaluation questions above to unlock download access.
🔒 Zero Data Retention: Rendered locally via HTML5 Canvas. We never store or transmit your identity.
🛡️

CYVEXIS OFFICIAL SECURITY ADVISORY

ZERO-TRUST IDENTITY POLICY // MANDATORY USER GUIDELINE

⚠️ Cyvexis will NEVER ask you for your passwords, two-factor authentication codes, or sensitive account credentials. If anyone contacts you asking for these credentials under our name, do not engage. Report the attempt immediately or report any issue to our official channels:

✉️ Official Security Desk: cyvexis.cybersecurity@gmail.com
📸 Official Instagram: @cyvexis