Exam Bundle

The public service remains available while arbitrary external clients cannot reach the administrative port. That observation would verify another scenario: A cloud virtual machine hosts an external service but also exposes SSH administration to the entire internet. The corrective step for that other scenario is: Restrict management ingress to approved access paths and enable auditable privileged authentication. But Brookside Manufacturing is evaluating: A cloud incident reviewer sees a suspicious credential used from an unusual location but lacks an inventory of what resources the token can access. The necessary outcome is: The compromised principal is disabled or constrained and the review identifies all affected authorized resources.

Data-flow evidence confirms approved regions for primary data and disaster-recovery copies. That observation would verify another scenario: A cloud application serves customer records in several regions without checking where regulated personal information may legally reside. The corrective step for that other scenario is: Apply data-classification and residency requirements to storage, backups, replicas and logging paths. But Brookside Manufacturing is evaluating: A cloud incident reviewer sees a suspicious credential used from an unusual location but lacks an inventory of what resources the token can access. The necessary outcome is: The compromised principal is disabled or constrained and the review identifies all affected authorized resources.

An anonymous test cannot list or read confidential objects and sanctioned public assets remain accessible through reviewed policy. That observation would verify another scenario: A cloud object storage container allows anonymous listing because it was created with a public access template. The corrective step for that other scenario is: Enforce private access by default, explicit policy review and organization-level public-exposure guardrails. But Brookside Manufacturing is evaluating: A cloud incident reviewer sees a suspicious credential used from an unusual location but lacks an inventory of what resources the token can access. The necessary outcome is: The compromised principal is disabled or constrained and the review identifies all affected authorized resources.

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 Silvercrest University finding instead concerns: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. It does not demonstrate the required correction. The decisive test remains: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Silvercrest University finding instead concerns: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. It does not demonstrate the required correction. The decisive test remains: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Silvercrest University finding instead concerns: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. It does not demonstrate the required correction. The decisive test remains: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Silvercrest University is evaluating: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The necessary outcome is: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Silvercrest University is evaluating: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The necessary outcome is: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Silvercrest University is evaluating: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The necessary outcome is: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Highland Education finding instead concerns: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. It does not demonstrate the required correction. The decisive test remains: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Highland Education finding instead concerns: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. It does not demonstrate the required correction. The decisive test remains: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 application encrypts customer data but stores the encryption key in the same publicly readable configuration file. It does not demonstrate the required correction. The decisive test remains: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Highland Education is evaluating: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The necessary outcome is: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Highland Education is evaluating: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The necessary outcome is: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate. That observation would verify another scenario: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. The corrective step for that other scenario is: Validate the full certificate chain, identity and validity interval against trusted roots rather than ignoring verification errors. But Highland Education is evaluating: An application encrypts customer data but stores the encryption key in the same publicly readable configuration file. The necessary outcome is: An unprivileged user cannot retrieve key material even when able to read ordinary application configuration.

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 Harborline Logistics finding instead concerns: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. It does not demonstrate the required correction. The decisive test remains: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Harborline Logistics finding instead concerns: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. It does not demonstrate the required correction. The decisive test remains: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Harborline Logistics finding instead concerns: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. It does not demonstrate the required correction. The decisive test remains: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Harborline Logistics is evaluating: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The necessary outcome is: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Harborline Logistics is evaluating: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The necessary outcome is: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Harborline Logistics is evaluating: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The necessary outcome is: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 developer uses an unsalted fast checksum function to store user passwords in the authentication database. It does not demonstrate the required correction. The decisive test remains: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Maplewood Schools finding instead concerns: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. It does not demonstrate the required correction. The decisive test remains: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Maplewood Schools finding instead concerns: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. It does not demonstrate the required correction. The decisive test remains: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Maplewood Schools is evaluating: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The necessary outcome is: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Maplewood Schools is evaluating: A developer uses an unsalted fast checksum function to store user passwords in the authentication database. The necessary outcome is: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 developer uses an unsalted fast checksum function to store user passwords in the authentication database. The necessary outcome is: Two identical test passwords produce different stored verifiers and no plaintext or fast unsalted hashes remain.

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 Timberline Foods finding instead concerns: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. It does not demonstrate the required correction. The decisive test remains: The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate.

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 Timberline Foods finding instead concerns: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. It does not demonstrate the required correction. The decisive test remains: The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate.

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 Timberline Foods finding instead concerns: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. It does not demonstrate the required correction. The decisive test remains: The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate.

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 Timberline Foods is evaluating: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. The necessary outcome is: The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate.

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 Timberline Foods is evaluating: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. The necessary outcome is: The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate.

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 Timberline Foods is evaluating: A service presents a certificate signed by an unknown private CA and the client accepts it without checking trust and hostname. The necessary outcome is: The client rejects an untrusted or wrong-name test certificate while accepting the legitimate service certificate.