Assess whether the incident is contained or still lateral (089c40)
August 31, 2026
SITUATION Over-privileged service account in production arrived with a contractor laptop leaving with a 40GB archive. Detection-engineering manager in a bank's SWIFT-adjacent environment still has an evidence gap on whether the incident is contained or still lateral.
DECISION Detection-engineering manager in a bank's SWIFT-adjacent environment must choose The incident is contained, Still lateral using over-privileged service account in production after a contractor laptop leaving with a 40GB archive. The question on that file is whether the incident is contained or still lateral.
HYPOTHESES TO TEST 1. Detection-engineering manager can defend The incident is contained from over-privileged service account in production after a contractor laptop leaving with a 40GB archive in a Cybersecurity challenge. 2. Detection-engineering manager cannot defend The incident is contained from over-privileged service account in production; Still lateral is what the extract actually supports after a contractor laptop leaving with a 40GB archive. 3. A contractor laptop leaving with a 40GB archive never reached the population in over-privileged service account in production — reopen intake, do not close the incident is contained. 4. Two facts in over-privileged service account in production after a contractor laptop leaving with a 40GB archive conflict for detection-engineering manager; hold this Third-Party and AI Security file.
ANALYSIS REQUIRED 1. Name the compensating control that would let detection-engineering manager release a reversible hold. 2. Test whether access is still live, already rotated, or only written as closed. 3. Check SIEM or identity logs in over-privileged service account in production for reuse after a contractor laptop leaving with a 40GB archive. 4. For this Cybersecurity Third-Party and AI Security file, read over-privileged service account in production against a contractor laptop leaving with a 40GB archive and write the one fact that would move the incident is contained for detection-engineering manager.
RECOMMENDATION Choose The incident is contained / Still lateral on this Cybersecurity / Third-Party and AI Security packet (over-privileged service account in production after a contractor laptop leaving with a 40GB archive). If over-privileged service account in production cannot force a Cybersecurity label under Third-Party and AI Security, stop. Do not invent missing evidence a bank's SWIFT-adjacent environment does not have.
COMMAND RETURNS - Bottom-line Cybersecurity option on the incident is contained, then the evidence in over-privileged service account in production, then the action for detection-engineering manager - Hypothesis scorecard against over-privileged service account in production: supported / rejected / untestable - Third-Party and AI Security finding in over-privileged service account in production that a second reviewer can re-perform - Missing page in over-privileged service account in production after a contractor laptop leaving with a 40GB archive, if any
Explore more
More Cybersecurity prompts
- Assess whether to isolate a plant or keep production running (abf9a1)
- Assess whether the incident is contained or still lateral (0cc66e)
- Assess whether the incident is contained or still lateral (9bf2a3)
- Assess whether the incident is contained or still lateral (466f02)
- Assess whether attribution is good enough to name an actor (1b10c0)
Explore related decision areas
- Content-attribution program lead must resolve whether monitoring detectsAI Governance Layer
- Whether deprecation will strand a downstream process from deprecation planAI Governance Layer
- Assess whether a provider should be suspended pending SIU (7c3c22)Fraud Detection
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

