You save $69.98
A payroll application uses fast unsalted SHA-256 hashes of employee passwords and argues that SHA-256 is cryptographically secure. What underlying security principle most directly explains the risk?
The observed facts point to the causal security principle: A fast general-purpose hash allows inexpensive offline guessing even if collision resistance is good. This is why the proportionate implementation response is use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan. The other answers either invent additional facts or mistake documentation or an adjacent safeguard for the actual cause.
The statement 'A single shared salt is equivalent to per-password unique salt' does not explain the observed exposure. It incorrectly treats a proxy, credential, or partial control as interchangeable with the missing evidence or authorization check. The evidence instead supports: A fast general-purpose hash allows inexpensive offline guessing even if collision resistance is good. This distinction determines why use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
The statement 'General-purpose hash speed is a desirable property for resisting offline password guessing' does not explain the observed exposure. It ascribes the exposure to a different or unsupported cause instead of the failing trust, lifecycle, data, or inspection boundary identified in the facts. The evidence instead supports: A fast general-purpose hash allows inexpensive offline guessing even if collision resistance is good. This distinction determines why use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
The statement 'Collision resistance by itself prevents high-throughput dictionary attacks' does not explain the observed exposure. It ascribes the exposure to a different or unsupported cause instead of the failing trust, lifecycle, data, or inspection boundary identified in the facts. The evidence instead supports: A fast general-purpose hash allows inexpensive offline guessing even if collision resistance is good. This distinction determines why use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
A payroll application uses fast unsalted SHA-256 hashes of employee passwords and argues that SHA-256 is cryptographically secure. Which validation evidence is most directly connected to this particular scenario?
The decisive acceptance evidence is: A controlled password-cracking benchmark shows significantly increased work per guess without breaking authentication capacity. It demonstrates that the intervention—Use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan—works in the scenario, rather than showing only a report, nominal configuration, or absence of alerts. An adverse test result would require remediation, not signoff.
Observing 'A test wordlist cracks many hashes quickly' would not prove that the proposed security fix succeeded. This is a proxy metric or adverse observation; it does not test both the intended security boundary and the permitted business function. To accept the remediation, the test must demonstrate: A controlled password-cracking benchmark shows significantly increased work per guess without breaking authentication capacity. That measures the actual result of use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
Observing 'Authentication migration stores fast hashes without a measured work factor' would not prove that the proposed security fix succeeded. This documents missing evidence or an incomplete test, not a verified outcome that establishes the control has operated effectively. To accept the remediation, the test must demonstrate: A controlled password-cracking benchmark shows significantly increased work per guess without breaking authentication capacity. That measures the actual result of use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
Observing 'Two users with the same password have the same stored hash without a unique salt' would not prove that the proposed security fix succeeded. This documents missing evidence or an incomplete test, not a verified outcome that establishes the control has operated effectively. To accept the remediation, the test must demonstrate: A controlled password-cracking benchmark shows significantly increased work per guess without breaking authentication capacity. That measures the actual result of use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
A payroll application uses fast unsalted SHA-256 hashes of employee passwords and argues that SHA-256 is cryptographically secure. Which follow-up uncertainty should be recorded in the risk register?
The remedy cannot eliminate every downstream risk. The directly relevant remaining issue is: Weak user-selected passwords remain guessable given enough resources and repeated credential reuse. This needs monitoring or a separate follow-up after implementing Use unique salts with an appropriately costed password-specific KDF such as Argon2id under a tested migration plan.
Authentication capacity must be benchmarked, but performance overhead is different from human-chosen low-entropy passwords remaining guessable.
Directory confidentiality needs safeguards, yet it is separate from the remaining weakness of reused or predictable user passwords.
Migration completeness is a deployment obligation, not the specific threat from weak and reused secrets after adoption of a strong KDF.
Two collaborating hospitals need to compute an aggregate patient metric without disclosing their individual record sets to the other party. What should the security team do first to correct the demonstrated weakness?
The case shows: Two collaborating hospitals need to compute an aggregate patient metric without disclosing their individual record sets to the other party. The preferred intervention—Assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity—directly corrects that deficiency. The security reason is that conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. It is scoped to an enforceable control decision, unlike a policy label or unrelated improvement.
Selecting 'Send both hospitals' raw records to the other participant and encrypt only during transfer' would not be the best response to this case. This focuses on only a portion of the workflow or leaves the decisive control or evidence gap in place. The actual gap is: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. The more defensible control is Assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Selecting 'Publish fine-grained results that allow individual patient reconstruction' would not be the best response to this case. It may affect an adjacent security task, but it does not supply the complete boundary-specific intervention demanded by these facts. The actual gap is: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. The more defensible control is Assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Selecting 'Compute everything in one untrusted central service with plaintext inputs' would not be the best response to this case. It may affect an adjacent security task, but it does not supply the complete boundary-specific intervention demanded by these facts. The actual gap is: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. The more defensible control is Assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Two collaborating hospitals need to compute an aggregate patient metric without disclosing their individual record sets to the other party. What underlying security principle most directly explains the risk?
The observed facts point to the causal security principle: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. This is why the proportionate implementation response is assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity. The other answers either invent additional facts or mistake documentation or an adjacent safeguard for the actual cause.
The statement 'A shared database automatically enforces secure multiparty confidentiality' does not explain the observed exposure. The absolute conclusion claims a guarantee that the scenario and the technical trust boundary do not support. The evidence instead supports: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. This distinction determines why assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
The statement 'An aggregate always preserves privacy regardless of group size' does not explain the observed exposure. The absolute conclusion claims a guarantee that the scenario and the technical trust boundary do not support. The evidence instead supports: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. This distinction determines why assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
The statement 'TLS ensures the compute provider cannot read the plaintext it receives' does not explain the observed exposure. The absolute conclusion claims a guarantee that the scenario and the technical trust boundary do not support. The evidence instead supports: Conventional encrypted transport protects data in transit but does not hide each party's plaintext from the computation host. This distinction determines why assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Two collaborating hospitals need to compute an aggregate patient metric without disclosing their individual record sets to the other party. Which test or observation would provide the clearest evidence that the correction worked?
The decisive acceptance evidence is: A pilot produces the expected aggregate while tests cannot recover one hospital's raw records from the permitted transcript. It demonstrates that the intervention—Assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity—works in the scenario, rather than showing only a report, nominal configuration, or absence of alerts. An adverse test result would require remediation, not signoff.
Observing 'A participating hospital can reconstruct the other side's raw records' would not prove that the proposed security fix succeeded. This is a proxy metric or adverse observation; it does not test both the intended security boundary and the permitted business function. To accept the remediation, the test must demonstrate: A pilot produces the expected aggregate while tests cannot recover one hospital's raw records from the permitted transcript. That measures the actual result of assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Observing 'Authorized transcript analysis exposes one party's private input' would not prove that the proposed security fix succeeded. This is a proxy metric or adverse observation; it does not test both the intended security boundary and the permitted business function. To accept the remediation, the test must demonstrate: A pilot produces the expected aggregate while tests cannot recover one hospital's raw records from the permitted transcript. That measures the actual result of assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Observing 'The computation output includes individual-level identifiers' would not prove that the proposed security fix succeeded. This is a proxy metric or adverse observation; it does not test both the intended security boundary and the permitted business function. To accept the remediation, the test must demonstrate: A pilot produces the expected aggregate while tests cannot recover one hospital's raw records from the permitted transcript. That measures the actual result of assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Two collaborating hospitals need to compute an aggregate patient metric without disclosing their individual record sets to the other party. Even if the primary action succeeds, which specific risk may remain?
The remedy cannot eliminate every downstream risk. The directly relevant remaining issue is: Small groups and auxiliary data may still allow inference from otherwise correct aggregate outputs. This needs monitoring or a separate follow-up after implementing Assess secure multiparty computation or appropriate privacy-preserving aggregation with leakage analysis and verified output integrity.
Performance may constrain deployment, but the stated residual confidentiality concern is inference from small aggregate groups and external auxiliary knowledge.
Input integrity is a distinct risk and does not specifically permit reconstructing another hospital's small-group patient characteristics.
Population-size disclosure is a narrower metadata concern, while small-cell results combined with auxiliary data can reveal sensitive individual attributes.
A messaging platform encrypts every TLS session with a long-term static key exchange and retains years of packet captures. What should the security team do first to correct the demonstrated weakness?
The case shows: A messaging platform encrypts every TLS session with a long-term static key exchange and retains years of packet captures. The preferred intervention—Adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys—directly corrects that deficiency. The security reason is that if an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. It is scoped to an enforceable control decision, unlike a policy label or unrelated improvement.
Selecting 'Reuse the same symmetric session key across every connection indefinitely' would not be the best response to this case. This weakens an existing safeguard or uses indiscriminate changes, increasing exposure instead of selectively correcting the demonstrated weakness. The actual gap is: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. The more defensible control is Adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
Selecting 'Continue static key exchange and rotate only the certificate once per year' would not be the best response to this case. This focuses on only a portion of the workflow or leaves the decisive control or evidence gap in place. The actual gap is: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. The more defensible control is Adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
Selecting 'Encrypt captured traffic archives with a stronger storage cipher but leave TLS handshakes unchanged' would not be the best response to this case. This focuses on only a portion of the workflow or leaves the decisive control or evidence gap in place. The actual gap is: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. The more defensible control is Adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
A messaging platform encrypts every TLS session with a long-term static key exchange and retains years of packet captures. Which statement correctly distinguishes the observed control weakness?
The observed facts point to the causal security principle: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. This is why the proportionate implementation response is adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys. The other answers either invent additional facts or mistake documentation or an adjacent safeguard for the actual cause.
The statement 'Long-term static key exchange provides strong forward secrecy automatically' does not explain the observed exposure. It ascribes the exposure to a different or unsupported cause instead of the failing trust, lifecycle, data, or inspection boundary identified in the facts. The evidence instead supports: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. This distinction determines why adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
The statement 'Storage encryption protects captured wire traffic after a server key compromise' does not explain the observed exposure. It ascribes the exposure to a different or unsupported cause instead of the failing trust, lifecycle, data, or inspection boundary identified in the facts. The evidence instead supports: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. This distinction determines why adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
The statement 'Session-key reuse prevents historical decryption following key exposure' does not explain the observed exposure. It ascribes the exposure to a different or unsupported cause instead of the failing trust, lifecycle, data, or inspection boundary identified in the facts. The evidence instead supports: If an old session's secret derives from a long-term compromised private key, historical captures may be decryptable. This distinction determines why adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
A messaging platform encrypts every TLS session with a long-term static key exchange and retains years of packet captures. Which finding is the strongest acceptance evidence for the recommended control?
The decisive acceptance evidence is: A test compromise of the current certificate key does not reveal previously established session keys. It demonstrates that the intervention—Adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys—works in the scenario, rather than showing only a report, nominal configuration, or absence of alerts. An adverse test result would require remediation, not signoff.
Observing 'An expired static handshake remains accepted' would not prove that the proposed security fix succeeded. This is a counterexample to successful enforcement: a prohibited action still succeeds or an expected boundary remains untested. To accept the remediation, the test must demonstrate: A test compromise of the current certificate key does not reveal previously established session keys. That measures the actual result of adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
Observing 'Compromise of the current server key reveals yesterday's session keys' would not prove that the proposed security fix succeeded. This is a proxy metric or adverse observation; it does not test both the intended security boundary and the permitted business function. To accept the remediation, the test must demonstrate: A test compromise of the current certificate key does not reveal previously established session keys. That measures the actual result of adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
Observing 'A new session uses an old key without independent ephemeral exchange' would not prove that the proposed security fix succeeded. This documents missing evidence or an incomplete test, not a verified outcome that establishes the control has operated effectively. To accept the remediation, the test must demonstrate: A test compromise of the current certificate key does not reveal previously established session keys. That measures the actual result of adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
A messaging platform encrypts every TLS session with a long-term static key exchange and retains years of packet captures. Even if the primary action succeeds, which specific risk may remain?
The remedy cannot eliminate every downstream risk. The directly relevant remaining issue is: Already exposed application plaintext and endpoint memory dumps remain outside transport forward-secrecy guarantees. This needs monitoring or a separate follow-up after implementing Adopt ephemeral authenticated key exchange with forward secrecy and rotate session secrets independently of certificate keys.
Client compatibility affects migration, but it is different from already exposed plaintext and volatile endpoint secrets that transport forward secrecy cannot revoke.
Operational continuity is important, yet a valid forward-secret handshake does not retroactively remove plaintext or memory dumps acquired by an attacker.
Application authorization remains important, but it is not the confidentiality boundary of previously extracted plaintext or endpoint memory.
Please check your mailbox for a message from support@examlabs.com and follow the directions.
