Assess whether legal hold and forensics must precede reboot (9d6ba7)

SITUATION Cloud-security architect is responsible for legal hold and forensics in a law firm, using a client-matter data store with over-privileged service account in production as the only working extract. Packet captures showing SMB to a previously quiet subnet is what reset the timeline for this Cybersecurity Exposure Management file.

DECISION Cloud-security architect in a law firm with a client-matter data store must choose Contain now / Monitor / Escalate / Hold using over-privileged service account in production after packet captures showing SMB to a previously quiet subnet.

HYPOTHESES TO TEST 1. Packet captures showing SMB to a previously quiet subnet is noise around an already-controlled Exposure Management process in a law firm with a client-matter data store, given over-privileged service account in production. 2. Packet captures showing SMB to a previously quiet subnet is the event in over-privileged service account in production that forces Contain now for cloud-security architect under Cybersecurity. 3. Over-privileged service account in production shows a one-file miss after packet captures showing SMB to a previously quiet subnet, not a Exposure Management program failure. 4. Over-privileged service account in production cannot decide legal hold and forensics yet after packet captures showing SMB to a previously quiet subnet; hold is the only Cybersecurity close a law firm with a client-matter data store can defend.

ANALYSIS REQUIRED 1. Separate a scoped exception from an unbounded exposure a law firm with a client-matter data store has not measured. 2. Map identities, standing privileges, and last-use timestamps in over-privileged service account in production to the blast radius of packet captures showing SMB to a previously quiet subnet. 3. Name the compensating control that would let cloud-security architect release a reversible hold. 4. For this Cybersecurity Exposure Management file, read over-privileged service account in production against packet captures showing SMB to a previously quiet subnet and write the one fact that would move legal hold and forensics for cloud-security architect.

RECOMMENDATION Choose Contain now / Monitor / Escalate / Hold on this Cybersecurity / Exposure Management packet (over-privileged service account in production after packet captures showing SMB to a previously quiet subnet). The follow-on Exposure Management action is what cloud-security architect does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Cybersecurity option on legal hold and forensics, then the evidence in over-privileged service account in production, then the action for cloud-security architect - Hypothesis scorecard against over-privileged service account in production: supported / rejected / untestable - Regulatory or exam hook Exposure Management would cite - Exposure Management finding in over-privileged service account in production that a second reviewer can re-perform