CISSP Practice Test

Answer: C
RTO is the targeted duration within which a business process must be restored after a disruption to avoid unacceptable consequences, which matches the 4-hour figure derived during BIA. RPO instead measures acceptable data loss in time (how much data, not downtime, can be lost). MTTR is an operational/technical repair-time metric, not a business-impact-derived target. MTD is the absolute outer limit of tolerable downtime and is typically larger than or equal to the RTO, not the target itself the question describes.

Answer: C
Option C is correct: Data sovereignty means the same dataset answers to the access, retention, disclosure and transfer laws of every country whose territory holds a copy, so a multi-region cloud deployment can be bound simultaneously by GDPR Chapter V transfer rules, the US CLOUD Act and local data-localization statutes. Option B gets the doctrine backwards; long-arm statutes extend a court's reach to out-of-jurisdiction parties, and the CLOUD Act shows a foreign-stored copy can be compelled from the provider. Option D is a preservation duty triggered by anticipated litigation; it applies regardless of location and does not create the conflict between jurisdictions' laws. Option A misstates a defunct mechanism; the EU-US Safe Harbor framework was invalidated by the Court of Justice in Schrems I (2015) and never authorized unrestricted holding of anyone's data.

Answer: C
Option C is correct: Criminal liability, with its penal consequences, demands proof beyond a reasonable doubt, whereas most civil claims are decided on the preponderance of the evidence, so the same investigation can fall short of a conviction yet support a damages award, and an investigation planned for criminal referral must meet the stricter evidentiary rigor from the start. Option B reverses the hierarchy; beyond a reasonable doubt is the highest standard and belongs to criminal cases, while clear and convincing is an intermediate standard used for particular civil claims. Option D splits the standard in a way no court does; every element of a criminal offense, not only intent, must be proven beyond a reasonable doubt. Option A overstates the civil standard; preponderance is the default civil standard, and clear and convincing evidence is reserved for specific matters such as fraud or punitive damages.

Answer: D
Option D is correct: ISC2 lets a candidate sit the CISSP before meeting the five-year experience requirement; on passing, the candidate is designated an Associate of ISC2 and has up to six years to accumulate the five years of cumulative paid experience in two or more domains (isc2.org/certifications/associate). Option A misstates the waiver: the one-year reduction is granted for a qualifying four-year degree or an approved credential, never for passing the exam itself. Option B adds a retake that does not exist; the passing result stands while the Associate completes the experience inside the six-year window. Option C invents a provisional credential; ISC2 does not award the CISSP, provisionally or otherwise, until the experience is verified and endorsed.

Answer: B
Option B is correct: Due diligence is the knowing: the research, risk assessment and ongoing monitoring that establish what a reasonable organization would know. Due care is the doing: the prudent, proportionate action taken in response. An organization that assessed a risk and then did nothing showed diligence without care, and negligence claims typically allege a failure of one or both. Option D confines each to a single event; diligence continues after the deal closes and care is expected before, during and after any incident. Option C swaps the two terms; diligence is the investigation and care is the reasonable action, and both are continuing duties rather than a one-time correction. Option A reassigns the concepts to different audiences; both duties are owed generally and neither is defined by who the beneficiary is.

Answer: C
Option C is correct: ISC2's registration process has the candidate create an ISC2 account, click Schedule in the Courses and Exams section and then, in ISC2's words, be redirected to the Pearson website to finalize the exam appointment, with delivery in person at a Pearson VUE test center (isc2.org/register-for-exam). Option A invents chapter-hosted paper sessions; the CISSP is a computer-based adaptive exam delivered only at Pearson VUE test centers. Option B keeps the booking inside ISC2 and invents at-home delivery; the portal hands off to Pearson VUE, and ISC2 delivers the CISSP at test centers, not by remote proctoring. Option D names the wrong vendor; ISC2 exams are scheduled and delivered through Pearson VUE, and there is no application approval step before scheduling.

Answer: D
Option D is correct: Copyright attaches automatically to original works of authorship, and 17 U.S.C. 102 treats computer programs as literary works, so the literal source code is protected as expression while 102(b) excludes the underlying ideas, procedures and methods of operation from that protection. Option A protects confidentiality rather than expression; the protection evaporates the moment the code is lawfully disclosed or independently developed, and it does not cover published code at all. Option B protects source identifiers under the Lanham Act; the software's name and logo have nothing to do with the code as an expressive work. Option C protects the invention, not the expression; a patent covers a novel, non-obvious process or machine and would not stop someone from writing different code that infringes nothing.

Answer: D
Option D is correct: SLE = AV x EF = $500,000 x 0.40 = $200,000; a flood expected once every 4 years gives ARO = 1/4 = 0.25; ALE = SLE x ARO = $200,000 x 0.25 = $50,000. Option A reports the SLE as if it were the ALE; the $200,000 single-loss figure still has to be multiplied by the 0.25 annual rate. Option B inverts the frequency, treating one flood every four years as four floods per year, which multiplies the SLE by 4 instead of by 0.25. Option C multiplies the full asset value by the ARO and skips the exposure factor, pricing a total loss when the scenario destroys only 40% of the asset.

Answer: B
Option B is correct: Under the outline effective April 15, 2024, the CISSP is a three-hour computerized adaptive test of 100 to 150 items with a passing score of 700 out of 1000 scaled points; ISC2's outline page now lists the CAT format for the English, Chinese, German, Japanese and Spanish exams. Option A describes the retired six-hour linear form; the English exam has been adaptive since 2017 and the outline page no longer lists a linear version for any language. Option C has the format right but the scoring wrong; an adaptive exam is scored on a scaled 0 to 1000 range with 700 as the pass mark, not on a percentage of items correct. Option D describes the four-hour, 125-to-175-item CAT format ISC2 used from 2022 until the April 15, 2024 outline replaced it; the item range is now 100 to 150.

Answer: B
Option B is correct: The CISSP exam outline effective April 15, 2024 lists eight domains weighted Security and Risk Management 16%, Asset Security 10%, Security Architecture and Engineering 13%, Communication and Network Security 13%, Identity and Access Management 13%, Security Assessment and Testing 12%, Security Operations 13% and Software Development Security 10% (isc2.org/certifications/cissp/cissp-certification-exam-outline). Option A has the right count but the wrong leader; Security Architecture and Engineering is one of four domains at 13%. Option C has the right count but the wrong leader and figure; Identity and Access Management is weighted 13%, below Security and Risk Management. Option D names the right domain but the wrong count and weight; the outline has eight domains and Security and Risk Management carries 16%.

Answer: D
Under 45 CFR 164.402 an impermissible acquisition, access, use or disclosure of protected health information is presumed to be a breach unless the covered entity or business associate demonstrates a low probability that the information has been compromised, based on a risk assessment of at least four factors: the nature and extent of the information including re-identification risk, the unauthorized person involved, whether the information was actually acquired or viewed, and the extent to which the risk has been mitigated. Whether the file was opened is only one of those factors, not the test. A deletion attestation is mitigation evidence feeding the assessment. Demonstrated harm is not the standard, and 164.414 places the burden of proof on the entity.

Answer: A
The FTC Safeguards Rule requires a covered financial institution to notify the Commission as soon as possible and no later than 30 days after discovering a notification event involving the unencrypted information of at least 500 consumers; the firm's 900 records cross that threshold. There is no year-end aggregate filing in the rule. Notifying consumers may be required by other laws but does not satisfy the Commission reporting duty. The qualified individual's annual written report to the board is a separate element of the required information security program, and reporting is not conditioned on a finding of demonstrated harm.

Answer: A
SP 800-37 Rev. 2 defines the authorization to use as the decision employed when an organization chooses to accept the information in an existing authorization package produced by another organization, typically for cloud and shared systems and services. A common control authorization runs the other way: it covers controls a provider offers for inheritance by systems, after the common control provider's own package is reviewed. The framework's interim testing authorizations are not a production authorization based on someone else's package. Reciprocity supports reuse of assessment results, but it is not automatic and does not transfer an authorization boundary by contract.

Answer: C
Stateful firewalls primarily track connection state using Transport-layer (Layer 4) information such as TCP sequence numbers, flags (SYN/ACK/FIN), and port pairs to determine whether a packet belongs to an established session. Layer 1 deals with physical signaling and has no session concept. Layer 2 deals with MAC addressing and frames, not session state. While some stateful and next-gen firewalls incorporate application-layer awareness, classic stateful inspection is defined by its Layer 4 state-tracking, not exclusive Layer 7 operation.

Answer: C
Option C is correct: Network access control combines 802.1X authentication of the user or device with a posture assessment of the endpoint, checking patch level, antimalware and agent status and configuration, and steers non-compliant devices to a remediation network, closing the gap of an authorized user on an unhealthy machine. Option A describes authorization policy on the user; it never examines the health of the device that user is bringing onto the network. Option D describes MAC authentication bypass with profiling, the weak fallback for devices that cannot run a supplicant; a spoofed MAC passes, and no posture is checked. Option B describes post-admission intrusion detection; NAC's decision is made before the device is granted access, based on identity and posture.

Answer: D
Option D is correct: An 802.1Q VLAN splits one physical switch into separate broadcast domains, and an ACL or firewall at the routed boundary between the guest and finance VLANs decides what, if anything, may cross, so a compromised guest device has no Layer 2 path to the finance servers and only the permitted Layer 3 path. Option A separates wireless names, not networks; unless each SSID maps to its own VLAN with filtering, both land in the same broadcast domain and the guest device can still reach the servers. Option B authenticates whatever plugs into the server ports; it does nothing to control where traffic from an already-connected guest device may go. Option C is defense in depth, not segmentation: it relies on every server's local rules staying correct and on guest addresses staying predictable, and it still lets the guest traffic reach the server's interface.

Answer: B
Option B is correct: NIST SP 800-207 states the zero trust tenets: no implicit trust based on network location, per-session access decisions, dynamic policy using identity, device posture and context, and continuous monitoring, all aimed at the lateral movement that a perimeter model permits once an attacker is inside. Option C swaps one implicit trust for another; SP 800-207 evaluates user identity, device posture and context per request, and never grants network-wide access on a certificate. Option D confuses confidentiality with authorization; encryption protects traffic in transit but says nothing about whether the requester should reach the resource. Option A restates the perimeter model with a stronger front door; free internal movement after one check is exactly the implicit trust zero trust removes.

Answer: C
Option C is correct: WPA3-Personal replaces the WPA2 four-way handshake with SAE, which resists offline dictionary attacks on the passphrase, and WPA3-Enterprise uses 802.1X/EAP so each user authenticates with individual credentials; both close the eavesdropping and unauthorized-association weaknesses WEP and WPA2-PSK left open. Option A relies on TKIP, an RC4-based cipher the Wi-Fi Alliance deprecated; rotating a shared key every 90 days still leaves every user holding the same secret and the captured handshake crackable offline. Option B adds two obscurity measures: MAC addresses are sniffed and spoofed in seconds and a hidden SSID is broadcast in every probe response, so neither is an authentication factor. Option D reintroduces WPS PIN, whose eight-digit PIN is brute-forced in hours because the registrar validates each half separately (CERT VU#723755), undoing the protection WPA3 provides.

Answer: C
Option C is correct: The attacker sends small queries to open resolvers with the source address forged to the victim's, so the resolvers reflect large responses at the victim; response sizes many times the query size give the amplification, and the victims never sent the queries they are answering for (CISA alert TA13-088A). Option A is a covert channel that moves data out slowly and quietly; it neither spoofs the victim's address nor tries to saturate the victim's link. Option B describes an integrity attack on resolver caches that changes where names resolve; it does not flood bandwidth, and the scenario shows no altered records. Option D puts the flood in the wrong place and protocol: the resolver is the unwitting reflector, the victims receive UDP DNS responses, and no TCP handshake is being exhausted.

Answer: A
Option A is correct: An 802.1Q VLAN is only as isolating as the switch configuration that tags and filters frames: switch spoofing through auto-negotiated trunks, double tagging across a native VLAN and an administrator's mistake all create paths the design assumed impossible, so VLANs cannot be treated as air gaps. Option B gets the layer wrong; a VLAN is a Layer 2 broadcast domain, and hosts in different VLANs cannot exchange frames without a router or Layer 3 switch. Option C invents a protocol dependency; VLAN tagging operates below IP and confines IPv6 neighbor discovery and multicast to the VLAN just as it confines IPv4. Option D misreads trunking; carrying multiple tagged VLANs is what trunks are for, and the risk lies in misconfigured trunks and native VLANs, not in trunking itself.

Answer: D
Option D is correct: An on-path attacker succeeds by terminating two separate encrypted sessions, one with each victim, so the control that defeats the attack is authentication of the peer: each side validates the other's certificate against a trusted authority (and pins where appropriate), which the impostor cannot satisfy. Option C closes one insertion technique on one LAN; an attacker at a hotspot, an upstream router or a compromised proxy is unaffected, so it does not defeat the attack itself. Option A protects the wrong thing; unauthenticated Diffie-Hellman is the textbook victim of an on-path attacker, who simply runs a separate exchange with each party. Option B assumes the key was negotiated with the right peer; when the attacker is that peer on both legs, the cipher's strength is irrelevant.

Answer: C
SP 800-41 Rev. 1 distinguishes packet filtering, stateful inspection and application-proxy gatewaying. Only the proxy acts as an intermediary that terminates the client connection and establishes its own connection to the server, which is what allows it to parse, inspect and modify application content. A stateless packet filter decides on header fields and is unconcerned with payload. Stateful inspection adds connection tracking, so it can tell whether a packet belongs to an established session, but it does not reconstruct and rewrite application data. Address translation hides internal addressing and is not a content inspection mechanism at all.

Answer: A
NIST SP 800-121 Rev. 2 advises organizations to use the strongest Bluetooth security mode available for their devices, identifying Security Mode 4, Level 4 for devices supporting Secure Connections because it requires authenticated pairing and FIPS-approved algorithms, with Level 3 for older devices. Security Mode 1 devices never initiate security and the publication says they should never be used, so making them non-discoverable is not a substitute. A fleet-wide fixed passkey reintroduces a shared static secret and defeats authenticated pairing. Choosing service-level security alone is weaker than the link-level protection the current mode provides during establishment.

Answer: A
SP 800-77 Rev. 1 describes three IPsec architectures: gateway-to-gateway, remote access (host-to-gateway) and host-to-host. Connecting two sites so that ordinary hosts need no VPN software is the gateway-to-gateway case, and it uses tunnel mode because the original packet must be encapsulated inside a new packet addressed between the gateways, which also conceals the internal addressing. Host-to-host with transport mode protects a single pair of systems and would require configuration on every host. Remote access describes individual client devices dialing in rather than a site link. Transport mode between gateways does not encapsulate the original header and so cannot carry traffic on behalf of the networks behind them.

Answer: A
NIST SP 800-77 Rev. 1 identifies Encapsulating Security Payload as the protocol that transports encrypted data and is the core IPsec security protocol, while the Authentication Header protocol provides integrity and authentication without confidentiality and is no longer recommended by that publication. For a requirement to protect sensitive file content, AH alone fails the primary objective. AH authenticates both peers rather than only one. The NAT difficulty with AH is real, but it is a deployment obstacle rather than the reason the design misses its confidentiality goal. Key negotiation is handled by IKEv2 independently of whether AH or ESP carries the traffic.

Answer: B
NIST SP 800-41 Rev. 1 describes a firewall policy that denies all traffic by default and permits only what is explicitly required, and it describes egress filtering as restrictions on traffic leaving the organization's network. Both findings are policy defects, so both need policy fixes. Reordering rules is a performance measure and leaves the permissive rule in place. Logging or detecting outbound abuse identifies exfiltration and command-and-control traffic after it has already left. Deep inspection and authentication improve what a rule does once it matches, but neither closes a default-permit posture or supplies the missing outbound restrictions.

Answer: A
ABAC evaluates multiple contextual attributes—user, resource, environment (time, device state), and action—through policy rules to make dynamic access decisions, matching the scenario's combination of department, classification, time, and device compliance. DAC lets resource owners grant access at their discretion, without this rule-based attribute evaluation. RBAC assigns permissions based on fixed roles rather than combining multiple dynamic attributes. Pure MAC relies on classification labels and clearance levels alone, not the broader attribute set (time, device compliance) described here.

Answer: C
Option C is correct: Just-in-time privileged access removes standing administrative credentials: a checked-out credential lives only for the approved task, so a stolen or misused one is valid for hours instead of indefinitely, which is the least-privilege objective behind NIST SP 800-53 AC-6 and CIS Control 5. Option A credits the time limit with an accountability benefit that actually comes from individual identities and session recording; a time-limited shared credential is still shared. Option B misreads the checkout as a factor; the temporary credential is still a single secret used in the same channel, and NIST SP 800-63B expects privileged access to keep MFA. Option D describes an approval-workflow property some PAM tools add; the time limit on the credential itself does not create separation of duties.

Answer: C
Option C is correct: In SAML 2.0 the identity provider is the authentication authority and the service provider is the relying party: the IdP verifies the credentials and returns a signed assertion, and the SP validates the signature and creates the session, so credentials never reach the application and the trust relationship becomes the critical control. Option A reverses the roles; if the SP authenticated locally there would be no federation, and the IdP is the party that authenticates. Option B describes OAuth 2.0 access tokens and a userinfo-style call, not SAML; a SAML assertion carries the identity and attributes itself. Option D puts a credential inside the assertion; SAML assertions carry authentication statements and attributes, never the password or its hash, and the SP verifies the signature, not a credential.

Answer: C
Option C is correct: RFC 6749 defines OAuth 2.0 as a framework for delegating scoped access to a resource, and an access token proves only that access was granted; OpenID Connect Core 1.0 layers an ID token with authenticated identity claims on the same flows, which is what makes it an authentication protocol. Option B misdescribes both; OAuth is not about API keys, and OpenID Connect is built on OAuth 2.0 rather than competing with it. Option A reverses the two; treating an OAuth access token as proof of identity is a documented anti-pattern, and delegation is OAuth's own job. Option D mixes in SAML; OAuth issues access tokens, not SAML assertions, and OpenID Connect's ID token is used in browser and mobile applications alike.

Answer: D
Option D is correct: In SAML 2.0 the identity provider is the authentication authority: it verifies the corporate credentials and returns a digitally signed assertion, and the SaaS application, acting as the service provider, trusts that assertion instead of ever seeing a password. Option A swaps protocols and directions: SAML issues assertions about the user to the SaaS application, whereas an OAuth access token authorizes a client to call an API. Option B assigns the service provider's job to the IdP; signature validation and session creation happen at the SaaS side after the assertion arrives. Option C describes account provisioning under SCIM (RFC 7644), a separate lifecycle function; SAML single sign-on does not depend on it and the IdP's role in the flow is authentication.

Answer: D
Option D is correct: Tightening a biometric threshold lowers false acceptances (Type II errors) while raising false rejections (Type I errors), so the crossover or equal error rate, where the two curves meet, gives one sensitivity-independent number for comparing systems (ISO/IEC 19795-1 calls it the equal error rate); a high-security deployment then tunes away from it toward fewer false acceptances. Option A describes the failure-to-enroll rate, a separate metric that is not averaged with anything. Option B describes a threshold so loose that false acceptances soar; the CER is the balance point, not the zero-rejection extreme. Option C confuses the crossover with a policy ceiling; the CER is where FAR equals FRR, and re-enrollment addresses template quality, not threshold tuning.

Answer: C
Option C is correct: Privileged access management exists because administrative accounts can disable controls and erase evidence: it removes standing privilege by vaulting and rotating the secrets, brokers time-bounded elevated sessions through checkout and approval, and records those sessions so actions taken under a shared administrative identity remain attributable. Option A describes identity governance and administration, the lifecycle management every account gets; it does not vault secrets or broker elevated sessions. Option B describes access management and single sign-on for ordinary users; it says nothing about privileged credentials or session recording. Option D describes a cloud access security broker's job, visibility and control over SaaS usage, not the control of administrative privilege.

Answer: B
Option B is correct: NIST SP 800-63B defines multifactor authentication as the use of two or more of the three distinct factor categories: something you know, something you have and something you are; a memorized password plus a possessed OTP token combines knowledge with possession. Option A stacks two inherence factors; two biometrics from one category remain single-factor, and SP 800-63B requires a biometric to be paired with a physical authenticator. Option C stacks two possession factors; stealing the bag that holds both defeats the scheme, which is exactly why a second category is required. Option D mislabels the questions: answers are memorized facts, so both credentials are knowledge factors, and SP 800-63B does not accept knowledge-based questions as an authenticator at all.

Answer: B
Option B is correct: Standardized job-function bundles assigned and revoked as a unit are roles, and the administrative benefit the ANSI/INCITS 359 RBAC standard was built for is exactly this: provisioning, de-provisioning and reviewing access per role rather than per individual. Option A names the wrong model and promises too much; ABAC (NIST SP 800-162) decides on attributes and policies rather than pre-built bundles, and attribute-driven decisions still require periodic review of the policies and attribute data. Option C confuses bundles with labels; MAC compares subject clearances against object classifications and is not defined by job functions at all. Option D hands permission decisions to individual owners, which is the per-person sprawl the enterprise is trying to escape, and DAC has no concept of a role bundle.

Answer: D
SP 800-63C-4 describes pairwise pseudonymous identifiers, in which the identity provider issues a different identifier for the same subscriber to each relying party, so the parties cannot correlate accounts by comparing values. Encryption in transit protects the identifier from outsiders but each relying party still learns the same value. A shorter assertion lifetime governs how long the assertion is usable, not whether identifiers are stable and comparable afterwards. Local hashing is deterministic, so two relying parties applying the same function to the same input still obtain matching values, and relying parties cannot be trusted to defeat their own correlation interests.

Answer: C
SP 800-63A-4 describes three identity assurance levels. The lowest supports the real-world existence of the claimed identity with limited evidence, the intermediate level requires additional evidence and more rigorous processes and may be performed remotely or on site, and the highest adds the requirement for a trained representative of the credential service provider to attend the proofing session and for at least one biometric characteristic to be collected so the subscriber can later be bound to the account. Federation assurance levels describe the protection applied to assertions between an identity provider and a relying party, which is a different dimension altogether.

Answer: A
This is session fixation, and the OWASP session management guidance names regeneration as the defense: the session identifier must be renewed after any privilege level change, authentication being the principal case, and the application should never accept a session identifier it did not generate. That invalidates whatever the attacker planted. The secure and httponly attributes protect an identifier from interception and script access, which addresses theft rather than fixation. A shorter idle timeout narrows the window but does not remove the flaw. Binding to address and user agent is a supplementary anomaly check that is easily matched by an attacker on the same network.

Answer: D
NIST SP 800-116 Rev. 1 sets a risk-based approach for facility access that designates controlled, limited and exclusion areas and maps the number of authentication factors to them: one factor for controlled, two for limited and three for exclusion areas, implemented through PIV authentication mechanisms appropriate to each. Applying a single factor everywhere ignores the escalation the model is built around, and log retention is not an authentication factor. Requiring two factors everywhere over-controls the lowest zone and under-controls the highest. Inverting the scale would place the weakest authentication where the assets are most sensitive.

Answer: A
Bell-LaPadula is a confidentiality-focused model (no read up, no write down) designed to prevent unauthorized disclosure, while Biba is an integrity-focused model (no read down, no write up) designed to prevent unauthorized or improper modification of data. Reversing these goals (option B) describes the models backward. Neither model addresses availability as its primary goal. The two models use opposite rule structures and are not interchangeable, since they protect different security properties.

Answer: A
A TPM is a dedicated, tamper-resistant hardware chip that securely generates and stores cryptographic keys and can measure and attest to the integrity of the boot process, matching the scenario exactly. A software-based key file lacks hardware tamper resistance and can be copied or exfiltrated more easily. A generic USB drive provides no cryptographic attestation or tamper protection. An unencrypted configuration file offers no protection for keys at all and is the opposite of a secure solution.

Answer: C
Option C is correct: Clean agents covered by NFPA 2001, such as FK-5-1-12 (Novec 1230), HFC-227ea (FM-200) and inert-gas blends, extinguish a fire without leaving conductive or corrosive residue and without wetting energized equipment, which is why they are the standard choice for rooms full of live server racks. Option A ignores that dry-chemical powder is corrosive and abrasive and contaminates every board it settles on, so it is avoided around electronics in favor of clean-agent portables. Option B overstates what pre-action buys: the dry pipe only guards against accidental discharge, and when a real fire trips the system it still floods energized equipment with water. Option D ignores that CO2 at extinguishing concentration is lethal; NFPA 12 requires pre-discharge alarms and evacuation, and it is not the preferred agent for normally occupied rooms.

Answer: D
Option D is correct: A signature under FIPS 186-5 is a hash of the document transformed with the signer's private key; verifying it with the public key proves the content is unaltered and that the private-key holder signed it, which supports non-repudiation, while the document itself stays readable unless separately encrypted. Option A adds availability, which no signature provides; a signature detects alteration but cannot restore or recover a document. Option B credits the signature with confidentiality it does not provide and denies the non-repudiation it exists for; key sharing is a key-management failure, not a property of the mechanism. Option C describes the wrong key; signing uses the signer's private key so anyone can verify, and encrypting a hash with the recipient's public key would prove nothing about the signer.

Answer: A
Option A is correct: Side-channel attacks such as Kocher's timing attacks, simple and differential power analysis, electromagnetic and acoustic emanation analysis and cache-timing attacks recover secrets from how the implementation behaves while it computes, which is why constant-time code, blinding and shielding are the countermeasures rather than a different algorithm. Option B describes key-management failures; a side channel extracts a properly generated key by observing the device that uses it. Option C describes protocol and configuration weaknesses; a side channel needs no downgrade because it observes the correctly configured implementation leaking. Option D describes classical cryptanalysis of the algorithm itself; a side channel attacks a mathematically sound cipher through its physical execution.

Answer: B
Option B is correct: Bell-LaPadula protects confidentiality with the simple security property (no read up) and the star property (no write down); together they stop a subject from learning information above its clearance and from leaking what it holds into a lower classification where less-cleared subjects could read it. Option A states the Biba integrity model's rules; Biba is the inverse of Bell-LaPadula and protects data from contamination, not from disclosure. Option C gets the write rule backwards; Bell-LaPadula permits writing upward (a blind write to a higher level leaks nothing) and forbids writing downward. Option D forbids reading downward, which Bell-LaPadula allows, since a highly cleared subject reading less sensitive data discloses nothing.

Answer: B
Option B is correct: Clark and Wilson (1987) model commercial integrity with constrained data items that may be changed only by certified transformation procedures, integrity verification procedures that confirm the data is in a valid state, and separation of duties among the people allowed to run those procedures, expressed as subject-program-object access triples. Option A describes the Brewer-Nash (Chinese Wall) model, whose purpose is preventing conflicts of interest, not enforcing well-formed transactions. Option C describes the Bell-LaPadula confidentiality model's state-machine approach; clearances and classifications play no part in Clark-Wilson. Option D describes Biba, the lattice-based integrity model the question contrasts Clark-Wilson against; Clark-Wilson has no integrity labels.

Answer: D
Option D is correct: PKI answers a compromised certificate with revocation: the CA lists the serial number on a signed certificate revocation list (RFC 5280) and answers OCSP queries about it (RFC 6960), and relying parties that check either source reject the certificate before its natural expiry. Option A treats an end-entity compromise as a root compromise; replacing the trust anchor is a last resort for a compromised CA key, and it would not tell relying parties this one certificate is bad. Option B gets path validation wrong; issuing a replacement leaves the compromised certificate fully valid until it expires or is revoked. Option C is a forward-looking strategy that limits future exposure but cannot inform anyone about a certificate that has already been issued and compromised.

Answer: A
Option A is correct: RSA is orders of magnitude slower than AES and can only encrypt a payload smaller than its modulus (about 190 bytes for RSA-2048 with OAEP), so it is reserved for transporting the short session key; AES then encrypts the bulk message quickly, and the key travels safely because only Party B's private key can unwrap it. Option B gets the division of labor wrong; RSA key transport supplies key distribution, not integrity, and neither layer as described provides integrity, which needs a MAC, an AEAD mode or a signature. Option C claims forward secrecy that RSA key transport cannot deliver: anyone who later obtains Party B's private key can unwrap every recorded session key, which is why TLS 1.3 (RFC 8446) dropped RSA key transport for ephemeral Diffie-Hellman. Option D invents a wear-out property; with proper padding, RSA does not weaken with the number of encryptions, and the reason for the split is performance and payload size, not key fatigue.

Answer: A
Option A is correct: The Trusted Computer System Evaluation Criteria (DoD 5200.28-STD) define the trusted computing base as the totality of protection mechanisms, including hardware, firmware and software, whose combination is responsible for enforcing the security policy; anything inside it can violate the policy if it fails, which is why it is kept as small and verifiable as possible. Option B ties the definition to an evaluation level; a component belongs to the TCB because the policy depends on it, whether or not it has been evaluated, and EAL4 is not a formal-verification level. Option C draws the boundary at the CPU mode; trusted user-mode processes such as the login program and security daemons enforce policy and are part of the TCB. Option D describes an organizational control baseline such as one tailored from NIST SP 800-53, a governance construct, not the system-level protection mechanisms the TCB names.

Answer: D
Option D is correct: Protection rings are hierarchical privilege levels enforced by the CPU: Ring 0 code may execute privileged instructions and touch kernel memory, while Ring 3 code must request services through controlled system calls, so a compromised application cannot directly subvert the kernel or other processes. Option A confuses privilege levels with cryptography; rings gate which instructions and memory regions code may use, and no encryption occurs when control passes between them. Option B mistakes a scheduler policy for a security boundary; ring level governs privilege, not CPU time, and the ring model makes no availability guarantee. Option C describes an administrative control over people, not a hardware privilege boundary; rings constrain executing code, and kernel changes are governed by change management, not by the ring model.

Answer: C
Option C is correct: Forward secrecy comes from deriving each session key through an ephemeral Diffie-Hellman exchange whose private values are discarded afterward, so a later leak of the server's long-term key gives an attacker nothing with which to recover past session keys; TLS 1.3 (RFC 8446) requires this by removing RSA key transport. Option A describes PKI revocation checking, which neither detects compromise nor protects recorded traffic; a revoked key can still decrypt captures made before revocation. Option B describes the opposite design; deriving session keys from the long-term key is exactly what destroys forward secrecy, and a broken RNG undermines ephemeral exchange. Option D reverses the relationship; per-session isolation is ordinary key separation, and forward secrecy is specifically about the long-term key not exposing earlier sessions.

Answer: C
Option C is correct: Under ISO/IEC 15408 (Common Criteria) the seven Evaluation Assurance Levels are assurance packages, from EAL1 functionally tested to EAL7 formally verified design and tested; the level says how thoroughly the claims in the security target were examined, while the security target itself says what the product claims to do. Option A overreads the rating; vulnerability analysis is one assurance family within the evaluation, and even EAL7 certifies rigor of examination against the stated target, not the absence of vulnerabilities. Option B confuses assurance with functionality; the functional requirements come from Part 2 and the security target, and a product can claim few functions at a high EAL or many at a low one. Option D mixes up two programs; cryptographic module validation is FIPS 140-3 under the CMVP, and its security levels 1 to 4 are unrelated to the EAL scale.

Answer: B
The order of volatility principle dictates collecting the most transient evidence first: CPU registers and cache change constantly and are lost the instant power/process state shifts, followed by RAM (lost on reboot/power-off), then network connection state (changes as sessions open/close), with disk contents being comparatively persistent and collected last. Option A reverses the entire order, starting with the most persistent artifact (disk) and ending with the most volatile (registers), which risks losing the most fragile evidence first. Option C and D scramble the sequence in ways that place persistent disk data ahead of more volatile network or register state, violating OOV and risking loss of transient evidence during collection.

Answer: C
A hot site is a fully operational, continuously synchronized duplicate environment capable of near-immediate failover, matching the minutes-long recovery described. A cold site provides only basic infrastructure (power, space, cooling) with no pre-installed systems or data, requiring days to weeks to become operational. A warm site has some equipment and partial data replication but requires additional setup and typically takes hours, not minutes, to fully activate. A mobile trailer with no pre-installed equipment is essentially a portable cold site and would not support minutes-long recovery.

Answer: B
Containment is the phase focused on limiting the scope and impact of an incident, such as isolating a compromised server from the network to stop ongoing exfiltration, which is exactly what's described. Preparation involves proactive readiness activities (plans, tooling, training) performed before an incident occurs. Detection and analysis involves identifying and scoping the incident, which has already occurred by the time isolation is triggered. Lessons learned is the post-incident review phase used to improve future response, not an active response action.

Answer: A
Option A is correct: A SIEM ingests, normalizes and correlates events from authentication systems, firewalls and endpoints in near real time, which is the cross-source correlation NIST SP 800-92 describes for detecting multi-stage attacks that no single tool's console would connect. Option B sees only endpoint telemetry; it cannot join firewall and authentication-server logs to the endpoint alert. Option C inspects packets on one network segment; it has no view of authentication logs or endpoint alerts and does no cross-source correlation. Option D automates response playbooks after something has been detected; it consumes the SIEM's correlated alerts rather than performing the correlation itself.

Answer: D
Option D is correct: SOAR platforms run playbooks that call other tools' APIs to isolate a host, disable an account or block an indicator when a defined alert condition fires, which is what turns a well-understood alert into an automatic action without waiting for an analyst. Option A can isolate its own host but cannot disable a directory account or coordinate actions across other tools, and tamper protection guards the agent, not the workflow. Option B improves detection by scoring anomalous behavior; it generates alerts and does not execute response actions. Option C produce the alert but do not act on it; a correlation rule raises an incident, and executing containment across the EDR, directory and firewall is orchestration.

Answer: B
Option B is correct: NIST SP 800-34 Rev. 1 defines MTD as the total time the business can tolerate the process being unavailable and RTO as the target for restoring the system, and it requires the RTO to be shorter than the MTD so that work recovery time, the period needed to restore data and resume processing after systems are back, also fits inside the limit. Option A imports an operational component-repair average; MTTR is not a business-continuity target, and the MTD is set by business impact, not by adding engineering metrics. Option C leaves no margin; a target equal to the limit fails as soon as the recovery runs long or the work recovery period is added, which is the harm the MTD marks. Option D mixes metrics; the RPO measures tolerable data loss in time before the disruption and has nothing to subtract from a downtime limit.

Answer: D
Option D is correct: Change management frameworks such as ITIL provide an emergency change path authorized by a small emergency change authority, with the risk assessment, backout plan and approval documented even if compressed, and a post-implementation review afterward; NIST SP 800-40 Rev. 4 likewise expects enterprises to plan expedited handling for actively exploited vulnerabilities. Option A leaves 90% of the estate exposed to a known active exploit for weeks; the pilot is sensible only as the first step of the emergency rollout, not as a reason to wait. Option B drops the documented approval and the review; verbal authority with paperwork weeks later gives no backout plan, no traceability and no evidence for auditors. Option C misclassifies the change: standard changes are low-risk, repeatable and pre-authorized, and an unscheduled production patch under active exploitation with no backout plan is none of those.

Answer: C
Option C is correct: NIST SP 800-61 and SP 800-86 frame this as a management decision: restoring before the intrusion is understood risks reinstating the vulnerability or the attacker's persistence and destroys evidence, while waiting has business cost, so the usual resolution is to image the affected systems quickly and restore while analysis continues on the images, with business and legal input. Option D hands the decision to a contract; notification clauses require timely notice and cooperation, and no policy obliges the business to stay down until an investigation ends. Option B reduces the decision to one metric; the RTO informs the impact side but ignores evidence preservation and the risk of restoring a still-compromised system. Option A misapplies a collection principle; the order of volatility sequences what is captured first, and imaging lets restoration proceed while analysis, not just collection, continues.

Answer: D
NIST SP 800-61 Rev. 3 layers the terms. An event is any observable occurrence involving computing assets, such as a login attempt. An adverse event is any event with a negative consequence regardless of cause, which includes power failures and natural disasters. A cybersecurity incident is an occurrence that actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality or availability of information or a system, or constitutes a violation or imminent threat of violation of law or policy. Only the confirmed unauthorized database access meets that definition; treating every event or every adverse event as an incident would flood the process and dilute the response.

Answer: B
Exercise types escalate in cost and risk, and the CISSP outline lists read-through and tabletop, walkthrough, simulation, parallel and full interruption. NIST SP 800-34 Rev. 1 describes tabletop exercises as discussion-based sessions where personnel discuss roles and responses to a scenario without deploying equipment or other resources, which makes them the right starting point for a plan nobody has exercised: they surface gaps and familiarize the team at almost no operational risk. A parallel test and a functional exercise require an operationally ready plan and trained staff. A full interruption test is the most disruptive form and is inappropriate when the business cannot tolerate an outage.

Answer: C
NIST SP 800-86 describes the forensic process as four basic phases in order: collection, examination, analysis and reporting. Examination forensically processes large volumes of collected data to extract what is relevant, analysis draws legally justifiable conclusions from the results of that examination, and reporting describes the actions taken, explains how tools and procedures were selected, and identifies what still needs to be done. Analyzing before examining means reasoning about data not yet extracted. Reporting before analysis publishes findings that have not been interpreted, which is exactly the error that undermines an investigation's credibility later.

Answer: B
SP 800-34 Rev. 1 defines three recovery phases, and reconstitution is the last: it validates system capability and functionality at the original or a new permanent location and then deactivates the plan. Validation may include functionality or regression testing, concurrent processing and data validation, and the system is declared recovered and operational by the system owners only after that testing succeeds. Deactivation also covers notifying users, finalizing activity logs, documenting the effort and incorporating lessons learned into plan updates. Moving damaged hardware, settling insurance and extended parallel running are business or engineering choices, not the step that closes the recovery.

Answer: B
Black-box testing simulates an external attacker who has no prior internal knowledge of the target system's architecture, source code, or credentials, matching the scenario exactly. White-box testing provides the tester full internal knowledge, including architecture and source code, which contradicts the 'no prior system knowledge' condition. Gray-box testing gives partial knowledge, and explicitly having 'full source code access' would actually make it white-box, not gray-box. Static code analysis examines source code without executing it and is a different technique from a simulated external attack.

Answer: B
A false positive occurs when a scanner flags a vulnerability that does not actually pose exploitable risk in the real deployed environment, exactly as described when manual verification shows the code path is unreachable. A true positive would mean the vulnerability is confirmed as genuinely exploitable, which is the opposite of what verification found. A false negative is a missed vulnerability that actually exists but wasn't detected, not a finding that was detected but doesn't apply. A true negative would mean no vulnerability was reported and none exists, which doesn't match this scenario where a finding WAS reported.

Answer: A
Option A is correct: A red team exercise pursues a defined objective by whatever path works, usually unannounced beyond a small control group, and the measured outcome is whether the blue team detected and responded; a penetration test instead aims to find and confirm as many exploitable weaknesses as possible within its scope. Option B describes a purple team exercise, which trades the realism of an unannounced campaign for faster detection tuning. Option C describes a security assessment or audit; a red team attacks live systems, which is what exercises detection and response. Option D describes exploitation-focused penetration testing; completeness of findings is the opposite of a goal-oriented campaign that takes one path in.

Answer: A
Option A is correct: Centralized log management (NIST SP 800-92) enables correlation across sources, so a logon on one host, a share access on another and a new service on a third become one visible lateral-movement sequence even though each event looks routine in its own log; forwarding also keeps copies an intruder cannot erase on the compromised host. Option C misdescribes the data and the benefit; events from different systems are distinct records, and retention cost is not the capability that per-system review lacks. Option B promises attribution that aggregation cannot supply; a shared or service account stays shared, and resolving it to a person requires individual accounts or session brokering. Option D misunderstands collection; an event a source never wrote does not exist to be re-requested, and completeness depends on the source's logging configuration.

Answer: D
Option D is correct: Static application security testing analyzes code or compiled binaries without running them, finding flaws early and pointing to the line while producing false positives for unreachable paths; dynamic testing sends inputs to the running application and observes behavior, catching configuration and environment issues static analysis cannot see, which is why NIST SP 800-218 expects both. Option B describes configuration auditing and performance testing; neither is application security testing of the code or the running application. Option A misplaces both; design review is not SAST, and reviewing source code is static, not dynamic, testing. Option C describes software composition analysis and fuzzing; SCA inventories dependencies rather than analyzing the code, and fuzzing is one dynamic technique, not the definition.

Answer: A
Option A is correct: An AICPA SOC 2 Type 2 report opines on both the design and the operating effectiveness of controls across a review period, so the auditor samples evidence of the control running throughout that window, typically six to twelve months. Option D inverts the test: exceptions show where the control failed, and the auditor must evidence the routine operations to conclude it worked. Option B is a Type 1 approach dressed up as Type 2; a point-in-time design test plus an unverified assertion does not evidence operation over the period. Option C samples one instance and extrapolates; Type 2 testing requires items drawn from across the whole period to show the control kept operating.

Answer: C
Option C is correct: NIST SP 800-115 separates the two: vulnerability scanning and assessment enumerate potential weaknesses across many systems without confirming exploitability, while penetration testing mimics an attacker to exploit a smaller set of paths and show what an attacker could actually reach, which is why the test needs explicit authorization and rules of engagement. Option A reverses the intrusiveness; exploitation is the active, potentially disruptive activity that most needs written authorization. Option B defines them by who performs them; either activity can be done internally or by a third party, and the difference is breadth versus exploitation. Option D invents a layer split and a universal mandate; both activities can target networks and applications, and no single rule requires an annual test everywhere.

Answer: A
NIST SP 800-115 notes that network scanning without host credentials can be performed internally and externally, that internal scanning usually uncovers more vulnerabilities than external scanning, and that testing from both vantage points gives the fuller picture; credentialed scanning adds the patch and configuration state of the host itself, which no external unauthenticated probe can see. More frequent scanning from the same vantage point repeats the same blind spot faster. Multiple engines add marginal coverage against the same limitation. A penetration test complements scanning but its annual cadence and narrower focus cannot substitute for systematic vulnerability identification.

Answer: A
SP 800-53A Rev. 5 provides exactly two finding values: satisfied and other than satisfied. A determination that could not be met makes the finding other than satisfied, and the assessor documents what failed and why so the organization can prioritize remediation and record it in a plan of action and milestones. Marking the control satisfied because most servers complied hides the gap from the authorizing official. Not applicable is reserved for controls that genuinely do not apply to the system, not for hosts that missed a setting. There is no partially satisfied value in the publication, so inventing one makes findings incomparable across assessments.

Answer: B
NIST SP 800-53 requires using internal system clocks to generate timestamps for audit records and comparing those clocks with an authoritative time source at a defined frequency, synchronizing when the difference exceeds the organization's threshold; SP 800-92 makes clock synchronization a foundation of usable log management because correlation across sources depends on a shared time base. Retaining logs longer preserves records that still cannot be ordered. Noting the analyst's clock does not correct the sources. Collector arrival times reflect network delay, buffering and forwarding intervals, so they are not a reliable substitute for the moment each event actually occurred.

Answer: A
NIST SP 800-53A Rev. 5 defines three assessment methods. Examine reviews artifacts such as the plan itself, interview holds discussions with personnel, and test exercises assessment objects under specified conditions to compare actual with expected behavior. The assessor here already has the document and the interview, so only exercising the plan, for instance through a recovery exercise, shows whether it works. Attestation is not one of the publication's assessment methods; a written certification is a management statement rather than evidence gathered by the assessor, and accepting it would repeat the weakness of relying on description alone.

Answer: D
The CISSP outline lists misuse case testing among security control testing techniques, and OWASP describes abuse cases as descriptions of intentional misuse derived by inverting each use case to ask how a hostile actor would subvert it. Requirements-based testing verifies what the system should do and so never exercises what it should refuse to do. Regression testing protects existing behavior across changes. Coverage analysis reports which code was executed without judging whether hostile scenarios were considered. Performance testing addresses capacity. Only misuse or abuse cases deliberately drive the application outside its intended use.

Answer: B
Need to know further restricts access within an already-authorized role so that a subject can only access the specific information required to perform their current task, which is why the accounts-payable employee is denied payroll data despite having general financial-system access. Separation of duties splits a sensitive process across multiple people to prevent fraud, which is a different control from restricting information access scope. 'Mandatory vesting' is not a security access-control concept. Due diligence refers to the reasonable care an organization exercises in managing risk, not an access-restriction mechanism.

Answer: D
The data owner (often a business-unit executive) has ultimate accountability for a dataset, including assigning its classification level and approving access decisions, because they best understand its business value and sensitivity. The data custodian implements technical controls (backups, access provisioning) on the owner's behalf but does not decide classification. System administrators perform operational tasks per established policy. End users merely consume data according to granted permissions and have no classification authority.

Answer: A
Option A is correct: GDPR Article 4(5) defines pseudonymization as processing that requires separately kept additional information to attribute data to a person, and Recital 26 states that such data remains personal data while truly anonymous information falls outside the Regulation; the practical difficulty is that auxiliary datasets often re-identify records believed anonymous. Option C inverts the transfer rules; pseudonymized data is personal data and needs Chapter V safeguards, while anonymous data needs none. Option B reverses Recital 26; removing direct identifiers while a key exists is pseudonymization and stays in scope, and the survival of some original dataset elsewhere does not make anonymous data personal. Option D keeps anonymous data in scope and invents requirement mappings; anonymized data is outside the regime, and pseudonymization is a safeguard, not a substitute for encryption at rest.

Answer: D
Option D is correct: The PCI Security Standards Council's tokenization guidance describes a token as a surrogate value mapped to the original only through a protected vault, so a stolen token yields nothing without the vault; that is what lets tokenized systems be removed from compliance scope, and it concentrates the risk in the vault. Option A describes hashing, which is neither reversible nor tokenization; the vault exists precisely so the issuer can recover the original when authorized. Option C again describes encryption with a shorter output; a true token has no key relating it to the original, so the obligation is protecting the vault, not a key. Option B describes format-preserving encryption; a reversible, key-based transformation is encryption and inherits its key-management and cryptanalytic exposure.

Answer: A
Option A is correct: NIST SP 800-88 (Guidelines for Media Sanitization) defines three levels: Clear resists only simple non-invasive recovery, Purge makes laboratory recovery infeasible, and Destroy additionally leaves the media unusable. Drives holding patient records that will leave the hospital's control for recycling warrant Destroy, which shredding, pulverizing or degaussing to the point of unusability achieves. Option B is a Clear-level technique in SP 800-88; it defeats casual recovery tools but is not the assurance level specified for high-sensitivity media leaving organizational control, and it cannot reach remapped or damaged sectors. Option C removes directory entries and overwrites only the blocks the new OS happens to use; the bulk of the patient data remains on disk and is trivially carved out with forensic tools. Option D encrypts nothing that matters: a quick format leaves the old data in place, and encrypting the empty volume afterward does not touch the remnants; cryptographic erase only works when the data was encrypted from the start.

Answer: A
Option A is correct: Retention limitation is the asset-security principle for sensitive personal and cardholder data: PCI DSS Requirement 3.2.1 limits storage of account data to what legal, regulatory and business purposes require and mandates secure deletion once that period ends, and privacy regimes apply the same storage-limitation rule to Social Security numbers. Option B applies an accounting schedule to data with no accounting purpose and leaves copies in backups and exports, so the deletion is neither minimal nor complete. Option C picks the longest schedule rather than the shortest defensible one, and archiving to tape is still retention, so the data keeps generating breach and discovery exposure. Option D keeps an indefinite copy; encryption reduces exposure but does not satisfy a retention limit, and PCI DSS treats encrypted account data in backups as stored account data.

Answer: B
Option B is correct: The information owner in NIST SP 800-18 and the asset owner in ISO/IEC 27001 Annex A 5.9 is the business role accountable for the data's value, classification and protection requirements, while the custodian is the operational role, usually IT, that runs the backups, permissions and monitoring the owner requires. Option A swaps the roles; classification and sign-off are ownership decisions, and the custodian carries them out rather than making them. Option C reduces ownership to funding and hands access decisions to a user; approving access is an owner responsibility and custodians are operators, not end users. Option D imports privacy-law roles; the individual described is the data subject, and controller and processor are GDPR terms, not the asset-security owner and custodian.

Answer: B
Baselines are starting points that organizations tailor, and when a control cannot be applied as written the recognized path is a compensating control that yields equivalent protection, documented with its rationale and approved by the responsible official. Here that might be surrounding the shared login with logged physical access, session recording and out-of-band identification of the operator. Silently deleting the control from the baseline loses the record of why the requirement is unmet. Marking an unimplemented control as implemented misstates the system's security posture to everyone who relies on it. Deferring to a replacement cycle still leaves the interim period unprotected and undocumented.

Answer: A
SP 800-88 Rev. 2 provides a sample certificate of sanitization and lists the details it should record, including manufacturer, model, serial number, media type and source, the sanitization method (clear, purge or destroy) and the specific technique, the tool used including version, the verification method, and the identity, title, date and signature of the person performing verification and validation. That record ties one identified device to one documented act. An asset register shows a replacement was bought, not what happened to the original. A screenshot lacks the device identifiers and the accountable signature. A waste manifest evidences transfer of custody by weight, not sanitization of a particular drive.

Answer: D
Establishing information and asset handling requirements means the protection travels with the asset. Media protection practice pairs marking that tells every handler the classification with encryption so that loss of a tape does not disclose its contents, and with accountability records that document custody at each transfer. A predictable collection schedule is an operational convenience and arguably tells an observer when the tapes are in transit. Environmental conditions in the vault preserve the media but do nothing about interception on the road. A non-disclosure agreement creates a legal remedy after disclosure rather than preventing it, and the courier should not be able to read the data at all.

Answer: B
SP 800-88 Rev. 2 treats cryptographic erase as a purge technique that works by sanitizing the keys, so it can only address data that was encrypted. The publication states the precondition that no sensitive data was previously stored on the media in plaintext form, and warns that cryptographic erase should not be trusted for media that has been backed up or escrowed unless the organization has high confidence in how those keys were stored and managed elsewhere. A recycler's certificate documents a downstream act, not whether the erase was effective. Key strength matters, but the acceptability question here turns on plaintext history and key copies. Nothing restricts cryptographic erase to resale scenarios.

Answer: C
Asset retention decisions must account for end of life and end of support, because an unsupported platform stops receiving the fixes the rest of the control set assumes. When the business cannot retire it on time, the defensible response combines technical containment such as network segmentation, restricted administrative access and enhanced monitoring with a time-boxed, formally accepted risk decision and review points. Signature-based endpoint protection does not remediate unpatched operating system vulnerabilities. An abrupt shutdown trades a security risk for a larger operational one without weighing either. Extended support helps but rarely covers every component, so it supplements containment rather than replacing it.

Answer: B
Option B is correct: Cross-site request forgery abuses ambient authority: because the browser attaches the session cookie to any request bound for the application, a forged form or image request from an attacker's page arrives looking like a legitimate authenticated action, which is why the OWASP CSRF Prevention Cheat Sheet prescribes synchronizer tokens and SameSite cookie attributes. Option A describes a replay attack by an on-path attacker; CSRF originates from a page the victim visits and involves no interception of traffic. Option C describes session fixation, in which the attacker plants a session ID; in CSRF the attacker never learns or sets the victim's session. Option D describes cross-site scripting; CSRF needs no script execution in the application's origin and never reads the cookie, it only causes the browser to send it.

Answer: D
Option D is correct: NIST SP 800-218 (SSDF practices PO.3 and PW.7 and PW.8) expects security checks to be built into the toolchain and automated, and in a pipeline that deploys on every merge the only control that keeps pace is a gate that runs at pipeline speed and blocks the build rather than reporting after the fact. Option A is a valuable periodic assessment outside the pipeline; it finds flaws months after the automated deploy shipped them. Option B protects the build hosts and the running service; neither control examines the code moving through the pipeline or can stop a bad build. Option C inserts a manual administrative gate that defeats continuous integration and still checks nothing about the code; approval belongs to release governance, not to the pipeline's technical controls.

Answer: A
Option A is correct: The OWASP SQL Injection Prevention Cheat Sheet lists prepared statements with parameterized queries as the primary defense because the query structure is fixed before user data is bound, so input can never be interpreted as SQL regardless of what it contains. Option B is OWASP's secondary defense; it helps, but free-text fields cannot be allow-listed tightly enough to be relied on as the primary barrier. Option C is the approach OWASP marks as strongly discouraged; escaping is database-specific, easy to get wrong and bypassed through encoding and alternate syntax. Option D is a compensating control in front of the flaw; rule sets are evaded with obfuscation and the injection remains in the code.

Answer: D
Option D is correct: NIST SP 800-218 (SSDF practice PW.1) and the Microsoft SDL place threat modeling in design, when data flows and trust boundaries are defined and a threat can still be removed by changing the architecture rather than by patching code later at far higher cost. Option A uses the model only to aim a test; by then the design flaws it would have surfaced are built and can only be confirmed, not prevented cheaply. Option B substitutes one activity for another; threat modeling informs security requirements but cannot replace them and has no architecture to analyze before design begins. Option C arrives after the architecture is fixed, so every design-level mitigation the model identifies now costs a rewrite; a data-flow diagram, not code, is what threat modeling needs.

Answer: A
Option A is correct: NIST SP 800-218 (SSDF practice PW.1) calls for threat modeling while designing the software, because a threat found on a data-flow diagram can be removed by changing the architecture, whereas the same threat found later can only be patched, at a cost that rises with every subsequent phase; STRIDE gives the structure for that early analysis. Option B arrives after the architecture is built; a design-level threat visible in review can be patched but no longer designed out cheaply. Option C uses the model only to confirm; by testing time the design is deployed and confirmation does nothing to lower the cost of the fix. Option D waits for the harm; a model built from a real breach is the most expensive way to learn what a design-phase analysis would have shown.

Answer: A
Option A is correct: The OWASP SQL Injection Prevention Cheat Sheet names prepared statements with parameterized queries as the primary defense: the database compiles the query structure first and binds the input afterward as data, so no input value can change the statement, whereas the other measures reduce exposure without removing the flaw. Option B is a secondary defense that breaks legitimate input such as a surname with an apostrophe and cannot cover free-text fields; validation narrows the attack surface but does not fix the concatenation. Option C is defense in depth for the aftermath; a limited account reduces the damage of a successful injection but leaves the injection possible. Option D is OWASP's second option and only safe when the procedure itself avoids dynamic SQL; a procedure that concatenates its arguments is injectable just like the application was.

Answer: D
Option D is correct: Everything served to the browser is public to the user: view-source, developer tools or a proxy exposes the JavaScript verbatim, so hard-coded database credentials (CWE-798) give any visitor direct authenticated access to the database. Option A frames a performance worry and assumes browsers connect to the database directly; the significant concern is disclosure of the secret, not pool exhaustion. Option B muddles caching with transport security; whether or not TLS or a cache is involved, the credentials are readable in the delivered file itself. Option C invokes an unrelated control; the same-origin policy governs script access between origins and has no bearing on secrets printed in a script.

Answer: B
Option B is correct: A library that was clean when selected becomes vulnerable the day a CVE is published against it, so NIST SP 800-218 and OWASP's guidance on vulnerable and outdated components call for an inventory of components (an SBOM) that is continuously checked against vulnerability feeds, which is what lets an organization answer which applications are affected within hours. Option A freezes known-vulnerable versions in place; pinning gives reproducibility, but without monitoring and upgrading, every later disclosure stays unpatched. Option C addresses license risk and provenance; a signed, properly licensed library can still ship a critical vulnerability. Option D cannot inventory dependencies or match them to disclosed vulnerabilities; DAST observes behavior from the outside and misses library flaws the test inputs never trigger.

Answer: D
The NIST Secure Software Development Framework in SP 800-218 organizes practices into four groups: Prepare the Organization, so that people, processes and technology are ready to develop secure software; Protect the Software, covering protection of components and releases from tampering and unauthorized access; Produce Well-Secured Software, covering design and implementation with minimal vulnerabilities; and Respond to Vulnerabilities, covering identification and remediation of residual flaws. The cybersecurity framework functions describe enterprise risk outcomes rather than development practices, while the other options are generic lifecycle or operating stages that carry no security practice content of their own.

Answer: C
OWASP guidance on error handling is to show users a generic, non-revealing message with a unique identifier they can quote, while the detailed diagnostic information goes to server-side logs; the mishandling of exceptional conditions category in the current Top 10 reflects how often this goes wrong. Verbose errors disclose schema names, query structure, file paths and framework versions that accelerate attacks. Gating detail on a support role puts sensitive internals one authorization flaw away from disclosure. Changing the status code hides errors from monitoring without addressing disclosure. Returning nothing at all leaves users and support with no way to correlate the failure.

Answer: C
OWASP password storage guidance rejects fast general-purpose hashes including MD5, SHA-1 and SHA-256 for passwords, because their speed lets an attacker with the database make enormous numbers of guesses; the remedy is a purpose-built, tunable password hashing function, with Argon2id preferred and PBKDF2 with a high iteration count named where FIPS-140 validation is needed. Salting a fast hash defeats precomputed tables but not high-speed brute forcing of each entry. Reversible encryption means a key compromise discloses every password in cleartext. Choosing a longer digest changes the output size, not the per-guess cost that makes fast hashes unsuitable.

Answer: D
OWASP authorization guidance requires that access control decisions be enforced server side on every request, against the authenticated identity and the specific resource being requested, and warns against relying on what the client presents or conceals. Here authentication succeeded but no check tied the caller to the record, so the object-level decision is missing. Unguessable identifiers only make enumeration harder, leaving anyone who learns an identifier fully able to read the record. Signing requests proves which client sent the call rather than what it may access. Encrypting the identifier obscures its structure while still returning whatever record it resolves to.