Exam Bundle

A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key. That observation would verify another scenario: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The corrective step for that other scenario is: Combine confidentiality controls with isolated immutable backup retention and verified recovery testing. But Brookside Manufacturing is evaluating: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The necessary outcome is: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

A test harness confirms nonce uniqueness and altered ciphertext fails authentication. That observation would verify another scenario: A database uses a fixed initialization vector for repeated encryption of confidential records with a mode that requires unique nonces. The corrective step for that other scenario is: Use an authenticated encryption scheme with safely generated non-reused nonces and protected keys. But Brookside Manufacturing is evaluating: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The necessary outcome is: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

An unprivileged user cannot retrieve key material even when able to read ordinary application configuration. That observation would verify another scenario: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The corrective step for that other scenario is: Protect encryption keys with a managed key vault or HSM and enforce separate access and rotation controls. But Brookside Manufacturing is evaluating: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The necessary outcome is: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

Use an authenticated encryption scheme with safely generated non-reused nonces and protected keys. This is an appropriate control for a different issue: A database uses a fixed initialization vector for repeated encryption of confidential records with a mode that requires unique nonces. The Juniper Media finding instead concerns: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. It does not demonstrate the required correction. The decisive test remains: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

Renew the appropriate certificate and verify signature validity, chain, and trusted timestamp policy. This is an appropriate control for a different issue: A company signs email using an expired certificate and assumes recipients will continue to trust the signature indefinitely. The Juniper Media finding instead concerns: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. It does not demonstrate the required correction. The decisive test remains: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

Combine confidentiality controls with isolated immutable backup retention and verified recovery testing. This is an appropriate control for a different issue: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The Juniper Media finding instead concerns: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. It does not demonstrate the required correction. The decisive test remains: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

An unprivileged user cannot retrieve key material even when able to read ordinary application configuration. That observation would verify another scenario: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The corrective step for that other scenario is: Protect encryption keys with a managed key vault or HSM and enforce separate access and rotation controls. But Juniper Media is evaluating: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The necessary outcome is: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain. That observation would verify another scenario: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The corrective step for that other scenario is: Use a memory-hard password hashing mechanism with unique salts and an appropriate work factor. But Juniper Media is evaluating: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The necessary outcome is: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

The device rotates to the new key and a verified authorized recovery procedure restores access successfully. That observation would verify another scenario: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The corrective step for that other scenario is: Plan protected recovery escrow and test key lifecycle operations before enforcing device-wide rotation. But Juniper Media is evaluating: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The necessary outcome is: A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites.

Validate the full certificate chain, identity and validity interval against trusted roots rather than ignoring verification errors. This is an appropriate control for a different issue: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. The Highland Education finding instead concerns: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. It does not demonstrate the required correction. The decisive test remains: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Renew the appropriate certificate and verify signature validity, chain, and trusted timestamp policy. This is an appropriate control for a different issue: A company signs email using an expired certificate and assumes recipients will continue to trust the signature indefinitely. The Highland Education finding instead concerns: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. It does not demonstrate the required correction. The decisive test remains: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Use a memory-hard password hashing mechanism with unique salts and an appropriate work factor. This is an appropriate control for a different issue: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The Highland Education finding instead concerns: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. It does not demonstrate the required correction. The decisive test remains: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Large files encrypt efficiently while only the intended recipient can recover the protected symmetric key. That observation would verify another scenario: A payment service uses RSA encryption directly on large files rather than a modern hybrid-encryption design. The corrective step for that other scenario is: Use a random symmetric data-encryption key and protect it with an appropriate public-key or key-agreement mechanism. But Highland Education is evaluating: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The necessary outcome is: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites. That observation would verify another scenario: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The corrective step for that other scenario is: Require approved modern TLS configurations on internal services and phase out deprecated algorithms. But Highland Education is evaluating: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The necessary outcome is: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

A test harness confirms nonce uniqueness and altered ciphertext fails authentication. That observation would verify another scenario: A database uses a fixed initialization vector for repeated encryption of confidential records with a mode that requires unique nonces. The corrective step for that other scenario is: Use an authenticated encryption scheme with safely generated non-reused nonces and protected keys. But Highland Education is evaluating: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The necessary outcome is: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Use an authenticated digital signature or message-authentication mechanism where sender authenticity is required. This is an appropriate control for a different issue: A file-transfer workflow hashes files with SHA-256 and concludes that this alone proves who sent the file. The Eastshore Energy finding instead concerns: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. It does not demonstrate the required correction. The decisive test remains: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Combine confidentiality controls with isolated immutable backup retention and verified recovery testing. This is an appropriate control for a different issue: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The Eastshore Energy finding instead concerns: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. It does not demonstrate the required correction. The decisive test remains: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Protect encryption keys with a managed key vault or HSM and enforce separate access and rotation controls. This is an appropriate control for a different issue: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The Eastshore Energy finding instead concerns: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. It does not demonstrate the required correction. The decisive test remains: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Large files encrypt efficiently while only the intended recipient can recover the protected symmetric key. That observation would verify another scenario: A payment service uses RSA encryption directly on large files rather than a modern hybrid-encryption design. The corrective step for that other scenario is: Use a random symmetric data-encryption key and protect it with an appropriate public-key or key-agreement mechanism. But Eastshore Energy is evaluating: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The necessary outcome is: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites. That observation would verify another scenario: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The corrective step for that other scenario is: Require approved modern TLS configurations on internal services and phase out deprecated algorithms. But Eastshore Energy is evaluating: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The necessary outcome is: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

A test harness confirms nonce uniqueness and altered ciphertext fails authentication. That observation would verify another scenario: A database uses a fixed initialization vector for repeated encryption of confidential records with a mode that requires unique nonces. The corrective step for that other scenario is: Use an authenticated encryption scheme with safely generated non-reused nonces and protected keys. But Eastshore Energy is evaluating: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The necessary outcome is: The device rotates to the new key and a verified authorized recovery procedure restores access successfully.

Use an authenticated digital signature or message-authentication mechanism where sender authenticity is required. This is an appropriate control for a different issue: A file-transfer workflow hashes files with SHA-256 and concludes that this alone proves who sent the file. The Maplewood Schools finding instead concerns: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. It does not demonstrate the required correction. The decisive test remains: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

Validate the full certificate chain, identity and validity interval against trusted roots rather than ignoring verification errors. This is an appropriate control for a different issue: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. The Maplewood Schools finding instead concerns: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. It does not demonstrate the required correction. The decisive test remains: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

Renew the appropriate certificate and verify signature validity, chain, and trusted timestamp policy. This is an appropriate control for a different issue: A company signs email using an expired certificate and assumes recipients will continue to trust the signature indefinitely. The Maplewood Schools finding instead concerns: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. It does not demonstrate the required correction. The decisive test remains: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

An unprivileged user cannot retrieve key material even when able to read ordinary application configuration. That observation would verify another scenario: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The corrective step for that other scenario is: Protect encryption keys with a managed key vault or HSM and enforce separate access and rotation controls. But Maplewood Schools is evaluating: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The necessary outcome is: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

A protocol scan rejects obsolete handshakes while approved internal applications negotiate supported cipher suites. That observation would verify another scenario: An engineer selects an obsolete cryptographic protocol for internal traffic because the network is not reachable directly from the internet. The corrective step for that other scenario is: Require approved modern TLS configurations on internal services and phase out deprecated algorithms. But Maplewood Schools is evaluating: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The necessary outcome is: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

The device rotates to the new key and a verified authorized recovery procedure restores access successfully. That observation would verify another scenario: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The corrective step for that other scenario is: Plan protected recovery escrow and test key lifecycle operations before enforcing device-wide rotation. But Maplewood Schools is evaluating: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The necessary outcome is: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

Use a random symmetric data-encryption key and protect it with an appropriate public-key or key-agreement mechanism. This is an appropriate control for a different issue: A payment service uses RSA encryption directly on large files rather than a modern hybrid-encryption design. The Brookside Manufacturing finding instead concerns: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. It does not demonstrate the required correction. The decisive test remains: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

Use an authenticated digital signature or message-authentication mechanism where sender authenticity is required. This is an appropriate control for a different issue: A file-transfer workflow hashes files with SHA-256 and concludes that this alone proves who sent the file. The Brookside Manufacturing finding instead concerns: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. It does not demonstrate the required correction. The decisive test remains: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

Protect encryption keys with a managed key vault or HSM and enforce separate access and rotation controls. This is an appropriate control for a different issue: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The Brookside Manufacturing finding instead concerns: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. It does not demonstrate the required correction. The decisive test remains: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

An unprivileged user cannot retrieve key material even when able to read ordinary application configuration. That observation would verify another scenario: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The corrective step for that other scenario is: Protect encryption keys with a managed key vault or HSM and enforce separate access and rotation controls. But Brookside Manufacturing is evaluating: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The necessary outcome is: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

A newly signed message validates under the current trust chain and invalid signatures are reported clearly. That observation would verify another scenario: A company signs email using an expired certificate and assumes recipients will continue to trust the signature indefinitely. The corrective step for that other scenario is: Renew the appropriate certificate and verify signature validity, chain, and trusted timestamp policy. But Brookside Manufacturing is evaluating: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The necessary outcome is: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.

The device rotates to the new key and a verified authorized recovery procedure restores access successfully. That observation would verify another scenario: An administrator rotates a disk-encryption key without preserving recovery policy and makes a test laptop unable to unlock its data. The corrective step for that other scenario is: Plan protected recovery escrow and test key lifecycle operations before enforcing device-wide rotation. But Brookside Manufacturing is evaluating: A team assumes that encrypting a backup makes its deletion by ransomware impossible and therefore performs no restore drills. The necessary outcome is: A simulated loss restores the correct version of data from a protected backup without relying on an exposed production key.