Pass ISC CISSP Exam in First Attempt Guaranteed!

Incorrect — it fails the original constraint. Late-running agents may not detect bootkit control before they initialize.

Incorrect — the measure Evaluate confidential computing or trusted execution appropriate to the threat model. addresses a different case: A service runs encrypted keys in memory on commodity shared virtual machines and fears hypervisor-level exposure.

Incorrect — this evidence applies to another case: A service runs encrypted keys in memory on commodity shared virtual machines and fears hypervisor-level exposure. The specified requirement here is An enterprise wants to stop modified boot components from launching on company laptops after physical theft.

This explains a later shift in requirements (A compliance officer needs attestations that laptops booted approved software.), not the failure of the current proposal.

This is an advantage of another design (Establish a trusted hardware/firmware baseline and perform validated firmware recovery before reimaging.), not the particular flaw of Rely only on a desktop antivirus agent that runs after the operating system boots.

This is a limitation elsewhere: An organization rebuilds servers after compromise but firmware state remains unverified and may be malicious. It does not explain the deficiency of the specified proposed approach.

This other observation is relevant to: An organization rebuilds servers after compromise but firmware state remains unverified and may be malicious.

An approved change without an executed test cannot prove operating effectiveness. The needed evidence is Tampered boot images fail signature verification and measured state alerts are recorded.

This demonstrates controls in another circumstance: A service runs encrypted keys in memory on commodity shared virtual machines and fears hypervisor-level exposure.

This remains inappropriate: Late-running agents may not detect bootkit control before they initialize.

This is a record of how the initial safeguard would be checked, not an action implementing the newly requested condition: Tampered boot images fail signature verification and measured state alerts are recorded.

This is the appropriate response to the original situation: Boot validation prevents unauthorized pre-OS components from silently becoming trusted. It does not directly meet the new condition.

This response addresses a different condition: An organization rebuilds servers after compromise but firmware state remains unverified and may be malicious. The present case requires the measure described by Evaluate confidential computing or trusted execution appropriate to the threat model.

Secrets must be decrypted during use and may be visible in unprotected memory. The proposal would not be defensible for this case.

This is appropriate for a later condition (A separate workload needs signing keys protected from application-server compromise.), but it does not directly resolve the initial need. Key use isolation requires a protected signing boundary, not only general process memory safeguards.

This is an advantage of another design (Enable verified secure boot and measured boot with platform keys managed under policy.), not the particular flaw of Conclude full-disk encryption always protects keys while a process is using them.

This is a limitation elsewhere: An enterprise wants to stop modified boot components from launching on company laptops after physical theft. It does not explain the deficiency of the specified proposed approach.

This explains a later shift in requirements (A separate workload needs signing keys protected from application-server compromise.), not the failure of the current proposal.

An approved change without an executed test cannot prove operating effectiveness. The needed evidence is Attestation and isolation tests verify the intended protected execution boundary.

This demonstrates controls in another circumstance: An organization rebuilds servers after compromise but firmware state remains unverified and may be malicious.

This other observation is relevant to: An enterprise wants to stop modified boot components from launching on company laptops after physical theft.

This is a record of how the initial safeguard would be checked, not an action implementing the newly requested condition: Attestation and isolation tests verify the intended protected execution boundary.

This is the appropriate response to the original situation: Memory isolation may mitigate certain privileged-host risks where ordinary disk encryption does not. It does not directly meet the new condition.

This remains inappropriate: Secrets must be decrypted during use and may be visible in unprotected memory.

Application scans cannot verify low-level boot firmware integrity. The proposal would not be defensible for this case.

This is appropriate for a later condition (The hardware vendor announces a critical TPM firmware update.), but it does not directly resolve the initial need. Firmware lifecycle maintenance is needed even after a trusted baseline is reestablished.

This response addresses a different condition: An enterprise wants to stop modified boot components from launching on company laptops after physical theft. The present case requires the measure described by Establish a trusted hardware/firmware baseline and perform validated firmware recovery before reimaging.

This is a limitation elsewhere: A service runs encrypted keys in memory on commodity shared virtual machines and fears hypervisor-level exposure. It does not explain the deficiency of the specified proposed approach.

This explains a later shift in requirements (The hardware vendor announces a critical TPM firmware update.), not the failure of the current proposal.

This is an advantage of another design (Evaluate confidential computing or trusted execution appropriate to the threat model.), not the particular flaw of Treat a clean application package scan as proof that platform firmware is trustworthy.

This demonstrates controls in another circumstance: An enterprise wants to stop modified boot components from launching on company laptops after physical theft.

This other observation is relevant to: A service runs encrypted keys in memory on commodity shared virtual machines and fears hypervisor-level exposure. In the current case, the assessed requirement is: An organization rebuilds servers after compromise but firmware state remains unverified and may be malicious. The organization has now implemented this response: Establish a trusted hardware/firmware baseline and perform validated firmware recovery before reimaging. Which observation would MOST directly demonstrate that the security objective was met.

An approved change without an executed test cannot prove operating effectiveness. The needed evidence is Platform attestation confirms trusted firmware version and secure boot measurements.