Pass Your CompTIA CAS-005 Exam Easy!

Model how a malicious actor could abuse recovery and identity proofing would not address the need for reassess workflow abuse and separation-of-duty threats.

Different subjects create different threat opportunities. The scenario does not present the alternate condition: a service grants the same permissions to batch automation and interactive staff. The proper immediate action is to reassess workflow abuse and separation-of-duty threats.

Draw explicit trust boundaries and test cross-tenant access paths would not address the need for reassess workflow abuse and separation-of-duty threats.

Building a path graph showing the privilege escalation route and placing a control at that edge would not address the need for rank feasible paths by prerequisites, exposure and business impact.

The current facts call for this action: rank feasible paths by prerequisites, exposure and business impact.

Model the shared failure node would not address the need for rank feasible paths by prerequisites, exposure and business impact.

The reported condition calls for this action: Use a lifecycle model to expose detection gaps at later stages.

The current facts call for this action: use a lifecycle model to expose detection gaps at later stages.

Attack patterns organize recurring exploitation behaviors. The scenario does not present the alternate condition: a design team wants reusable examples of how attackers abuse password reset workflows. The proper immediate action is to use a lifecycle model to expose detection gaps at later stages.

The current facts call for this action: identify unsanctioned cloud services and assess sensitive data exposure.

Information leakage can ease adversary reconnaissance. The scenario does not present the alternate condition: a website reveals sensitive internal service naming in public configuration files. The proper immediate action is to identify unsanctioned cloud services and assess sensitive data exposure.

The reported condition calls for this action: Identify unsanctioned cloud services and assess sensitive data exposure.

Model integrity and operational impacts would not prioritize credible espionage paths across supplier trust connections.

Threat models should not assume every actor is nation-state grade. The scenario does not present the alternate condition: a public campaign website sees repeated low-skill vandalism attempts. The proper immediate action is to prioritize credible espionage paths across supplier trust connections.

Prioritizing account takeover and transaction misuse threat scenarios would not prioritize credible espionage paths across supplier trust connections.

Model the shared failure node would not distinguish detective coverage from necessary preventative safeguards.

The current facts call for this action: distinguish detective coverage from necessary preventative safeguards.

Building a path graph showing the privilege escalation route and placing a control at that edge would not distinguish detective coverage from necessary preventative safeguards.

The reported condition calls for this action: Inventory public digital disclosures and reduce unnecessary exposure.

The current facts call for this action: inventory public digital disclosures and reduce unnecessary exposure.

Shadow assets cannot be excluded from threat modeling. The scenario does not present the alternate condition: an employee launches a SaaS tenant outside procurement without audit logging. The proper immediate action is to inventory public digital disclosures and reduce unnecessary exposure.

The current facts call for this action: model denial-of-service abuse and bound resource admission.

Nonbusiness telemetry can cross confidentiality boundaries. The scenario does not present the alternate condition: a batch processor logs personal fields to a broad telemetry channel. The proper immediate action is to model denial-of-service abuse and bound resource admission.

The reported condition calls for this action: Model denial-of-service abuse and bound resource admission.

Model how a malicious actor could abuse recovery and identity proofing would not address the need for model separate actor capabilities and constrain role design.

Internal location is not proof of authorization. The scenario does not present the alternate condition: an authorization design assumes all internal callers are trusted. The proper immediate action is to model separate actor capabilities and constrain role design.

Reassess workflow abuse and separation-of-duty threats would not address the need for model separate actor capabilities and constrain role design.

Prioritizing credible espionage paths across supplier trust connections would not address the need for model availability and integrity abuse proportionately to attacker capability.

The current facts call for this action: model availability and integrity abuse proportionately to attacker capability.

Model integrity and operational impacts would not address the need for model availability and integrity abuse proportionately to attacker capability.

The reported condition calls for this action: Use the Diamond Model to structure those linked observations.

The current facts call for this action: use the Diamond Model to structure those linked observations.

Attack patterns organize recurring exploitation behaviors. The scenario does not present the alternate condition: a design team wants reusable examples of how attackers abuse password reset workflows. The proper immediate action is to use the Diamond Model to structure those linked observations.