All practice questions

2232 questions

Question 1621Question

An organization deploys a centralized Privileged Access Management (PAM) solution to govern administrator access to production databases. When a database administrator requests a session, the PAM system first verifies their identity using a hardware token and PIN. Next, the PAM system evaluates an access policy matrix to determine if the session occurs within an approved maintenance window and applies a restricted read-only role for that specific database instance. Finally, the proxy engine writes a cryptographic audit log of all executed SQL queries. Which pillar of the Security AAA framework is being implemented when the PAM system evaluates the policy matrix to grant the restricted read-only role?

Show answer & explanation

Answer: Authorization

Answer

Authorization is the AAA pillar responsible for evaluating access policies and applying permission restrictions based on user roles and environmental context.
Evaluating an access policy matrix to assign specific roles, rights, or conditions (such as limiting permissions to a read-only role during specific maintenance windows) is the core function of Authorization within the AAA security framework.

Step-by-Step Solution

1
Analyze the action described in the target phase of the scenario.
The target phase evaluates an access policy matrix, checks environmental conditions (approved maintenance window), and assigns specific rights (restricted read-only role).
Identifying the functional behavior helps categorize it into one of the AAA components.
2
Differentiate between AAA pillars.
Authentication verifies identity (token/PIN). Authorization grants specific access permissions and roles based on context. Accounting logs and tracks activity (recording SQL queries).
Matching the scenario activity to definitions confirms the correct classification.
3
Select the matching AAA pillar.
Evaluating policy to grant specific permissions and restrict roles is explicitly the function of Authorization.
Authorization enforces access control parameters following successful authentication.

Key Concept

Authentication, Authorization, and Accounting (AAA) framework responsibilities
Question 1622Question

A security manager is updating an enterprise third-party risk management framework to enhance vendor oversight and supply chain resilience. Match each third-party governance control or evaluation artifact to its primary operational purpose.

Click a left item, then click its matching right item

Items

SOC 2 Type II Report
Software Bill of Materials (SBOM)
Right-to-Audit Clause
Hardware Root of Trust Verification

Matches

Show answer & explanation

Answer

SOC 2 Type II Report matches operational effectiveness evaluation over a period; Software Bill of Materials (SBOM) matches inventory visibility into code dependencies; Right-to-Audit Clause matches contractual authority to inspect vendor facilities and systems; Hardware Root of Trust Verification matches validating component integrity against supply chain tampering.
Each mechanism aligns directly with its primary role in vendor and supply chain risk oversight: SOC 2 Type II provides historical control effectiveness attestation; SBOM delivers code dependency transparency; Right-to-Audit provisions grant legal access for direct inspections; and Hardware Root of Trust verification mitigates physical supply chain tampering.

Step-by-Step Solution

1
Analyze third-party audit reports
Identify SOC 2 Type II as an attestation report that assesses control effectiveness over time.
SOC 2 Type I evaluates design at a point in time, whereas Type II tests operational effectiveness over a specified testing window.
2
Evaluate software supply chain visibility tools
Identify SBOM as the machine-readable inventory of software components.
Managing software supply chain risk requires visibility into underlying software dependencies.
3
Examine legal contractual mechanisms
Associate the Right-to-Audit clause with formal permission to inspect third-party controls and facilities.
Without an explicit audit provision in the contract, vendors are not obligated to grant access for on-site or technical inspections.
4
Assess hardware supply chain integrity mechanisms
Link Hardware Root of Trust Verification with checking physical hardware integrity.
Cryptographic chips and root-of-trust measurements ensure devices have not suffered interdiction or unauthorized component swaps.

Key Concept

Third-Party Risk Management and Supply Chain Oversight
Question 1623Question

An enterprise organization is updating its security governance framework following a comprehensive compliance audit. The Governance, Risk, and Compliance (GRC) team must establish clear operational boundaries between mandatory requirements and discretionary guidance across all departments. Which of the following governance components represent MANDATORY requirements that personnel or technical implementations must strictly adhere to? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: An Acceptable Use Policy (AUP) establishing high-level mandatory behavioral expectations and administrative rules across the enterprise.; A Technical Security Standard specifying compulsory baseline configurations, such as requiring AES-256 encryption for data at rest.

Answer

The Acceptable Use Policy (AUP) and the Technical Security Standard represent mandatory governance requirements.
In enterprise security governance, Policies and Standards are mandatory elements. An Acceptable Use Policy establishes top-level compulsory rules set by executive leadership, while a Technical Security Standard mandates explicit technical controls (such as mandatory encryption algorithms) that systems must implement without exception unless a formal variance is granted.

Step-by-Step Solution

1
Analyze enforceability levels in security governance documentation hierarchies.
Policies (such as an AUP) and Standards (such as encryption requirements) are mandatory enforcement tools.
Policies reflect executive management mandates, while standards mandate specific, non-negotiable technical or operational configurations.
2
Evaluate non-binding governance documentation types.
Guidelines and advisories represent discretionary guidance.
Guidelines provide best-practice recommendations that allow operational flexibility and lack mandatory compliance enforceability.
3
Distinguish documentation hierarchy tiers from technical operational controls.
Identity authentication frameworks define technical access control functions rather than governance document enforceability tiers.
AAA technical mechanisms execute access decisions but do not define organizational governance documentation rules.

Key Concept

Security Governance Hierarchy (Mandatory Policies & Standards vs. Discretionary Guidelines)
Question 1624Question

To align with newly enacted data privacy regulations, a financial institution's executive leadership issues an overarching directive declaring that all customer-facing applications must enforce data protection measures. The document establishes high-level business goals, defines organizational scope, and applies mandatorily to all employees, but deliberately omits technical algorithm choices, key lengths, and step-by-step administrative procedures. Which governance document tier does this directive represent?

Show answer & explanation

Answer: Policy

Answer

The executive directive represents a Policy because it is a mandatory, high-level statement of management intent and scope without technical specificity.
A security policy is a top-level governance document issued by senior management that sets the organization's security posture, objectives, and responsibilities. It is mandatory, applies broadly across the organization, and avoids technical details to remain resilient against technology changes.

Step-by-Step Solution

1
Analyze the enforceability and scope of the document described in the scenario.
The directive is mandatory for all personnel and issued directly by executive leadership.
Governance documentation tiers are categorized by enforceability level and organizational authority.
2
Evaluate the technical specificity of the document contents.
The document specifies organizational goals and scope but intentionally avoids naming specific algorithms or step-by-step configurations.
Policies provide top-level direction, whereas lower governance tiers like standards and procedures contain granular technical specifications.
3
Map the document characteristics to the governance document hierarchy.
High-level + Mandatory + Executive Authority = Policy.
This combination of characteristics uniquely defines an information security policy within formal governance frameworks.

Key Concept

Security Policy Hierarchy and Documentation Tiers
Question 1625Question

Match each cryptographic primitive or mechanism to its primary operational security function in an enterprise environment.

Click a left item, then click its matching right item

Items

Ephemeral Diffie-Hellman (ECDHE)
Hash-based Message Authentication Code (HMAC)
Cryptographic Salt with PBKDF2
Cipher Block Chaining (CBC) Mode

Matches

Show answer & explanation

Answer

Ephemeral Diffie-Hellman matches providing perfect forward secrecy; HMAC matches message integrity and authenticating origin; Cryptographic Salt with PBKDF2 matches protecting password stores against rainbow tables; Cipher Block Chaining Mode matches block-level sequential data confidentiality.
Ephemeral Diffie-Hellman provides key exchange with forward secrecy; HMAC ensures keyed message integrity and authentication; Salting prevents precomputed hash lookup attacks on credentials; CBC mode encrypts data blocks in sequence using feedback from previous blocks.

Step-by-Step Solution

1
Analyze Ephemeral Diffie-Hellman (ECDHE)
Identified requirement for session key isolation and forward secrecy.
Ephemeral key exchanges produce unique keys per session that do not depend on long-term private keys.
2
Analyze Hash-based Message Authentication Code (HMAC)
Identified requirement for message integrity combined with authentication using a shared secret.
Standard hashing only provides integrity; HMAC adds a secret key to provide origin verification.
3
Analyze Cryptographic Salt with PBKDF2
Identified requirement for password hashing defense against precomputed tables.
Salting adds random data per user password to defeat rainbow table lookups.
4
Analyze Cipher Block Chaining (CBC) Mode
Identified requirement for block cipher confidentiality via chaining.
CBC mode uses XOR operations with preceding blocks to randomize ciphertexts of repeating plaintext.

Key Concept

Cryptographic Primitives and Operational Security Functions
Question 1626Question

A security operations center analyst receives a high-severity alert from a network security monitoring system watching a dedicated deception host (honeypot) located inside a monitored subnet segment. The alert logs multiple inbound connection attempts on TCP port 22 originating from an external IP address. The analyst immediately submits an emergency change request to reconfigure the honeypot host's local firewall to block port 22 incoming traffic to mitigate the risk of compromise. Which of the following best evaluates the analyst's action?

Show answer & explanation

Answer: The analyst's action is flawed because honeypots are designed to attract and observe unauthorized activity, and blocking traffic prevents intelligence gathering.

Answer

The analyst's action is flawed because honeypots are designed to attract and observe unauthorized activity, and blocking traffic prevents intelligence gathering.
The correct answer highlights that a honeypot is a deception control specifically built to attract unauthorized network interactions to study adversary tactics, techniques, and procedures (TTPs). Applying inline block rules directly on the honeypot prevents analysts from gathering security intelligence and defeats the system's purpose.

Step-by-Step Solution

1
Analyze the function of the target security asset mentioned in the monitoring alert.
The target asset is identified as a honeypot (deception host) designed specifically to draw attack traffic into an isolated environment.
Understanding the baseline purpose of the monitored system is essential for proper incident response and alert triage.
2
Evaluate the analyst's proposed remediation action against security monitoring goals.
Blocking port 22 traffic on the honeypot prevents the system from fulfilling its purpose of gathering threat intelligence and observing attack tactics.
Honeypots rely on accepting unauthorized connections in a controlled environment to generate high-fidelity alerts and telemetry.
3
Select the option that correctly identifies the conceptual flaw in the analyst's response.
Recognizing that honeypot controls are intended for detection and intelligence rather than inline prevention leads to the correct option.
Modifying a honeypot to block scans disrupts network security monitoring and intelligence operations.

Key Concept

Honeypot Alerting and Deception Technology Monitoring
Estimated Time:1m 30s
Question 1627Question

A financial institution is evaluating the risk profile of its online identity verification service, which has an estimated Asset Value (AVAV) of $500,000\$500,000. A threat modeling report indicates that an unmitigated credential stuffing vulnerability has an Exposure Factor (EFEF) of 20%20\% per security incident. Threat intelligence metrics project an Annual Rate of Occurrence (AROARO) of 0.40.4 for this specific attack vector. Based on quantitative risk analysis principles, what is the Annual Loss Expectancy (ALEALE) associated with this risk?

Show answer & explanation

Answer: $40,000\$40,000

Answer

The Annual Loss Expectancy (ALEALE) associated with this risk is $40,000\$40,000.
The correct calculation uses the quantitative risk assessment formula ALE=SLE×AROALE = SLE \times ARO, where SLE=AV×EFSLE = AV \times EF. Multiplying the Asset Value ($500,000\$500,000) by the Exposure Factor (0.200.20) yields a Single Loss Expectancy of $100,000\$100,000. Multiplying $100,000\$100,000 by the Annual Rate of Occurrence (0.40.4) results in an Annual Loss Expectancy of $40,000\$40,000.

Step-by-Step Solution

1
Calculate the Single Loss Expectancy (SLESLE)
SLE=AV×EF=$500,000×0.20=$100,000SLE = AV \times EF = \$500,000 \times 0.20 = \$100,000
Single Loss Expectancy represents the monetary loss expected from a single realization of a risk event.
2
Calculate the Annual Loss Expectancy (ALEALE)
ALE=SLE×ARO=$100,000×0.4=$40,000ALE = SLE \times ARO = \$100,000 \times 0.4 = \$40,000
Annual Loss Expectancy scales the single loss amount by the expected annual frequency of occurrence.

Key Concept

Quantitative Risk Assessment (ALE Calculation)
Question 1628Question

An enterprise organization is procuring custom network appliances from a third-party manufacturer. To mitigate the risk of hardware supply chain tampering and unauthorized firmware modification during transit, the security team must establish a verification mechanism to validate device authenticity prior to deployment. Which of the following controls provides the MOST effective verification of hardware and firmware integrity upon receipt?

Show answer & explanation

Answer: Verifying the hardware root of trust and cryptographic signatures against the vendor's published measurements alongside a signed Software Bill of Materials (SBOM)

Answer

Verifying the hardware root of trust and cryptographic signatures against the vendor's published measurements alongside a signed Software Bill of Materials (SBOM)
The correct answer provides cryptographic proof of hardware and firmware authenticity. A hardware root of trust (such as a Trusted Platform Module) combined with cryptographic signature verification against a vendor-provided Software Bill of Materials (SBOM) allows the receiving organization to detect unauthorized hardware additions, firmware alterations, or supply chain interdiction prior to connecting the device to the production environment.

Step-by-Step Solution

1
Analyze the threat context in the scenario
Identified supply chain tampering and unauthorized firmware modification during transit as the primary risks.
Supply chain security requires direct verification of physical and logical components prior to commissioning.
2
Evaluate potential control mechanisms for hardware/firmware integrity
Determined that technical validation using hardware roots of trust (e.g., TPM/Secure Boot hashes) and signed SBOMs ensures components match expected vendor baselines.
Cryptographic attestations provide tamper-evident proof of component authenticity.
3
Differentiate technical integrity verification from administrative attestations and perimeter defenses
Ruled out SOC 2 reports, NDAs/ISAs, and WAF network controls as ineffective for detecting physical supply chain tampering prior to deployment.
Administrative reports and network firewalls do not inspect or validate hardware microcode or device component supply chain integrity.

Key Concept

Supply Chain Security and Hardware Integrity Verification
Question 1629Question

A United States healthcare provider operates a web portal that allows patients to view medical records and pay out-of-pocket expenses using credit cards. Which of the following regulatory compliance frameworks must the organization adhere to in order to protect patient health records and credit card transactions? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Health Insurance Portability and Accountability Act (HIPAA); Payment Card Industry Data Security Standard (PCI-DSS)

Answer

Health Insurance Portability and Accountability Act (HIPAA) and Payment Card Industry Data Security Standard (PCI-DSS) are the required compliance standards.
The Health Insurance Portability and Accountability Act (HIPAA) governs the privacy and security of patient medical records (PHI). The Payment Card Industry Data Security Standard (PCI-DSS) is an industry mandate required for any organization processing credit card payments. Because the web portal handles both medical records and payment card transactions, both frameworks apply.

Step-by-Step Solution

1
Identify the types of sensitive data described in the scenario.
The portal processes Protected Health Information (PHI) and Credit Card Holder Data (CHD).
Regulatory frameworks are determined by the specific categories of data processed and stored by the organization.
2
Match the identified data categories to their corresponding compliance mandates.
PHI falls under HIPAA regulations, while credit card processing falls under PCI-DSS standards.
HIPAA governs healthcare information privacy in the US, while PCI-DSS is required for processing credit card payments.

Key Concept

Regulatory Scope and Data Protection Frameworks
Estimated Time:1m 0s
Question 1630Question

A fintech enterprise is assessing security controls for an e-commerce API gateway with an Asset Value (AV) of $1,200,000\$1,200,000. Threat intelligence indicates an Annual Rate of Occurrence (ARO) of 0.250.25 for a major distributed denial-of-service (DDoS) attack. The Chief Risk Officer (CRO) sets a maximum acceptable Annual Loss Expectancy (ALE) threshold of $15,000\$15,000 for DDoS-related risks. Which of the following represents the maximum Exposure Factor (EFEF) that an implemented Web Application Firewall must achieve to keep residual risk within this threshold?

Show answer & explanation

Answer: 5%5\%

Answer

The maximum Exposure Factor (EFEF) required to remain within the risk threshold is 5%5\%.
The correct response accurately applies the quantitative risk equation ALE=AV×EF×ARO\text{ALE} = \text{AV} \times \text{EF} \times \text{ARO}. Substituting $15,000=$1,200,000×EF×0.25\$15,000 = \$1,200,000 \times \text{EF} \times 0.25 gives $15,000=$300,000×EF\$15,000 = \$300,000 \times \text{EF}. Solving for EF\text{EF} yields 15,000300,000=0.05\frac{15,000}{300,000} = 0.05, which equals 5%5\%. Any Exposure Factor higher than 5%5\% would exceed the Chief Risk Officer's $15,000\$15,000 annual risk threshold.

Step-by-Step Solution

1
Identify known variables from the scenario
Asset Value (AV)=$1,200,000(\text{AV}) = \$1,200,000, Annual Rate of Occurrence (ARO)=0.25(\text{ARO}) = 0.25, and target Annual Loss Expectancy (ALE)$15,000(\text{ALE}) \le \$15,000.
Extracting all required quantitative inputs is necessary before setting up the equation.
2
Recall the fundamental quantitative risk assessment formula
ALE=SLE×ARO=(AV×EF)×ARO\text{ALE} = \text{SLE} \times \text{ARO} = (\text{AV} \times \text{EF}) \times \text{ARO}
The formula links total asset value, exposure percentage, and frequency of occurrence to total annual financial risk.
3
Algebraically isolate the target variable (EFEF)
EF=ALEAV×ARO\text{EF} = \frac{\text{ALE}}{\text{AV} \times \text{ARO}}
Rearranging the equation allows solving directly for the unknown exposure threshold.
4
Substitute values and perform the calculation
EF=15,0001,200,000×0.25=15,000300,000=0.05=5%\text{EF} = \frac{15,000}{1,200,000 \times 0.25} = \frac{15,000}{300,000} = 0.05 = 5\%
Computing the fraction yields the maximum allowable post-mitigation exposure factor.

Key Concept

Quantitative Risk Analysis (Solving for Exposure Factor given ALE, AV, and ARO)
Estimated Time:2m 0s
Question 1631Question

A financial enterprise is migrating its transaction processing infrastructure to a cloud-native container environment. The Chief Information Security Officer (CISO) mandates that every production container host and image must enforce an identical set of mandatory minimum security configurations, including root access restrictions, disabled unused daemons, and read-only root filesystems. Which of the following security governance documents should the security architecture team publish to define these compulsory minimum configuration settings across all host platforms?

Show answer & explanation

Answer: A security baseline

Answer

The correct document type is a security baseline, which specifies the mandatory minimum configuration settings and hardening requirements for systems across an organization.
A security baseline defines the minimum mandatory security state and configuration settings that systems, services, or platforms must maintain. Because the scenario calls for mandatory technical configuration settings (such as read-only filesystems and root restrictions) enforced across all container deployments, a security baseline is the exact governance document required.

Step-by-Step Solution

1
Analyze the scenario requirements
The requirement specifies mandatory, uniform, low-level technical configuration settings (disabling unneeded daemons, restricting root privileges, enforcing read-only filesystems) across all production container platforms.
Identifying whether the requirement is high-level, technical, mandatory, or discretionary determines its position in the governance hierarchy.
2
Evaluate governance document characteristics
High-level rules are defined by policies; technical metrics/protocols are set by standards; step-by-step instructions are detailed in procedures; optional advice is conveyed in guidelines; and minimum mandatory technical configurations are established by baselines.
Security governance relies on strict documentation taxonomy to ensure operational enforcement.
3
Select the governance document matching compulsory technical hardening settings
A security baseline directly satisfies the need for compulsory minimum system configuration benchmarks.
Baselines serve as the reference standard against which system compliance and configuration drift are measured.

Key Concept

Security Baseline Definitions and Governance Hierarchy
Estimated Time:1m 30s
Question 1632Question

An e-commerce enterprise is performing a quantitative risk assessment for its core order processing cluster, which has an estimated Asset Value (AVAV) of $750,000\$750,000. Security metrics indicate that a ransomware incident affecting this cluster has an Annualized Rate of Occurrence (AROARO) of 0.200.20 and an Exposure Factor (EFEF) of 40%40\%. To mitigate this risk, the enterprise plans to deploy an Endpoint Detection and Response (EDR) control costing $18,000\$18,000 annually. This safeguard will reduce the EFEF to 10%10\% without affecting the AROARO. What is the net annual financial benefit, in dollars, of implementing this security safeguard?

Show answer & explanation

Answer: 27000

Answer

The net annual financial benefit of implementing the EDR safeguard is $27,000.
To determine the net annual benefit, first calculate the initial Annualized Loss Expectancy (ALE1=$750,000×0.40×0.20=$60,000ALE_1 = \$750,000 \times 0.40 \times 0.20 = \$60,000). Next, calculate the post-mitigation Annualized Loss Expectancy (ALE2=$750,000×0.10×0.20=$15,000ALE_2 = \$750,000 \times 0.10 \times 0.20 = \$15,000). The gross annual loss reduction is $60,000$15,000=$45,000\$60,000 - \$15,000 = \$45,000. Finally, subtracting the annual safeguard cost of $18,000\$18,000 yields a net annual benefit of $27,000\$27,000.

Step-by-Step Solution

1
Calculate the initial Single Loss Expectancy (SLE1SLE_1) and initial Annualized Loss Expectancy (ALE1ALE_1).
SLE1=$750,000×0.40=$300,000SLE_1 = \$750,000 \times 0.40 = \$300,000; ALE1=$300,000×0.20=$60,000ALE_1 = \$300,000 \times 0.20 = \$60,000.
Establish baseline quantitative risk exposure before implementing controls.
2
Calculate the post-mitigation Single Loss Expectancy (SLE2SLE_2) and post-mitigation Annualized Loss Expectancy (ALE2ALE_2).
SLE2=$750,000×0.10=$75,000SLE_2 = \$750,000 \times 0.10 = \$75,000; ALE2=$75,000×0.20=$15,000ALE_2 = \$75,000 \times 0.20 = \$15,000.
Determine the residual financial risk remaining after control deployment.
3
Calculate the gross annual risk reduction (ΔALE\Delta ALE).
ΔALE=ALE1ALE2=$60,000$15,000=$45,000\Delta ALE = ALE_1 - ALE_2 = \$60,000 - \$15,000 = \$45,000.
Find the total annualized loss prevented by the control.
4
Calculate the net annual financial benefit.
Net Benefit=ΔALESafeguard Cost=$45,000$18,000=$27,000\text{Net Benefit} = \Delta ALE - \text{Safeguard Cost} = \$45,000 - \$18,000 = \$27,000.
Account for control implementation overhead to determine overall monetary savings.

Key Concept

Quantitative Risk Analysis (ALE, SLE, ARO, and Net Safeguard Cost-Benefit Analysis)
Question 1633Question

A financial enterprise operates a high-frequency trading platform with continuous uptime requirements. A vendor releases a critical security patch addressing an unauthenticated remote code execution flaw in the underlying operating system. The security team must address this threat across all host instances while ensuring system stability and compliance with strict service level agreement (SLA) commitments. Which of the following patch management strategies best balances rapid threat mitigation with continuous operational availability?

Show answer & explanation

Answer: Implement a canary deployment in a representative staging environment, validate stability through automated regression testing, and execute a phased rolling update across production nodes.

Answer

Implement a canary deployment in a representative staging environment, validate stability through automated regression testing, and execute a phased rolling update across production nodes.
Testing patches in a staging environment prior to initiating a canary release and rolling updates ensures software stability, verifies compatibility, and maintains high availability SLAs during patch deployment.

Step-by-Step Solution

1
Analyze the operational context and security requirement.
Identified the need to remediate a critical remote code execution vulnerability on high-availability hosts without breaching uptime SLAs.
Direct production patching without pre-deployment testing risks widespread system instability.
2
Evaluate deployment strategies for safety and continuous service.
Staging validation combined with canary testing and rolling updates isolates potential failures while maintaining operational uptime.
Rolling updates apply changes incrementally across host groups, ensuring remaining nodes continue handling live traffic.

Key Concept

Staged Patch Deployment and Rolling Update Strategies
Estimated Time:1m 30s
Question 1634Question

During a physical security assessment, security auditors observe an unauthorized individual entering a secured facility by following closely behind a credentialed staff member through a badge-access door. Once inside the facility, the individual secretly records an administrator entering sensitive credentials onto a workstation keyboard from a nearby seating area. Which of the following social engineering vectors were executed during this physical security breach? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Tailgating; Shoulder surfing

Answer

The correct social engineering attack vectors are tailgating and shoulder surfing.
Tailgating is correctly identified because the intruder physically followed a credentialed user through an access point without authenticating. Shoulder surfing is correctly identified because the intruder observed the physical entry of confidential credentials onto a workstation keyboard.

Step-by-Step Solution

1
Analyze the physical access mechanism described in the scenario.
The unauthorized individual entered the secure facility by following an authorized employee through a badge-access door without credential verification, defining tailgating.
Tailgating relies on physical proximity to bypass electronic entry controls.
2
Analyze the information-gathering method described in the scenario.
The intruder visually observed and recorded an administrator entering sensitive credentials onto a keyboard from a nearby location, defining shoulder surfing.
Shoulder surfing relies on direct observation of user inputs or displays without verbal interaction.

Key Concept

Physical Social Engineering Vectors (Tailgating and Shoulder Surfing)
Question 1635Question

A Chief Information Security Officer (CISO) is restructuring the enterprise security documentation hierarchy to streamline compliance and operational governance across cloud and on-premises environments. Match each security governance document type to its corresponding operational characteristic.

Click a left item, then click its matching right item

Items

Organizational Security Policy
Technical Security Standard
System Security Baseline
Security Guideline

Matches

Show answer & explanation

Answer

Organizational Security Policy matches high-level executive directives; Technical Security Standard matches mandatory technical rules; System Security Baseline matches minimum compulsory initial configurations; Security Guideline matches discretionary advice.
Security governance frameworks establish a clear hierarchy: policies reflect executive leadership directives and scope; standards define specific mandatory technologies and rules; baselines set the minimum compulsory security state for systems; guidelines offer discretionary best practice recommendations.

Step-by-Step Solution

1
Analyze governance documentation hierarchy levels by enforceability and scope.
Identified policies and standards as mandatory high/medium level directives, baselines as minimum configuration requirements, and guidelines as non-mandatory advice.
Security governance relies on separating mandatory directives from discretionary guidance.
2
Map Organizational Security Policy to executive directives.
Policy aligns with high-level executive mandates that set organizational rules and security intent.
Policies are overarching governance frameworks set by leadership.
3
Differentiate between mandatory standards/baselines and non-mandatory guidelines.
Standards dictate mandatory technical specifications, baselines define minimum deployment configurations, and guidelines offer optional suggestions.
Standards and baselines are strictly compulsory, while guidelines provide operational flexibility.

Key Concept

Security Policy and Governance Documentation Hierarchy
Question 1636Question

Following an unannounced infrastructure outage, a financial services company executes its business continuity plan for a core payment gateway. The organization's Business Impact Analysis (BIA) specifies a Maximum Tolerable Downtime (MTD) of 6 hours6\text{ hours} and a Recovery Point Objective (RPO) of 15 minutes15\text{ minutes}. Technical recovery teams successfully restore the primary database from an automated snapshot generated 10 minutes10\text{ minutes} prior to the incident, completing baseline platform recovery in 2.5 hours2.5\text{ hours}. However, post-restoration data integrity verification, transaction reconciliation, and security testing require an additional 4 hours4\text{ hours} before operational sign-off is granted and production traffic is resumed. Which of the following conclusions best evaluates the organization's business continuity performance against its established metrics?

Show answer & explanation

Answer: The organization satisfied its RPO requirement but failed to meet its MTD objectives because total operational recovery, combining system restoration and Work Recovery Time (WRT), exceeded the allowable limit.

Answer

The organization satisfied its RPO requirement but failed to meet its MTD objectives because total operational recovery, combining system restoration and Work Recovery Time (WRT), exceeded the allowable limit.
The solution correctly evaluates both parameters separately. RPO is satisfied because the data loss duration (10 minutes10\text{ minutes}) was less than the allowable target (15 minutes15\text{ minutes}). However, the total operational downtime comprises both the technical recovery (2.5 hours2.5\text{ hours}) and the work recovery/reconciliation phase (4 hours4\text{ hours}), totaling 6.5 hours6.5\text{ hours}. Since 6.5 hours6.5\text{ hours} exceeds the Maximum Tolerable Downtime (6 hours6\text{ hours}), the overall continuity performance breached MTD limits.

Step-by-Step Solution

1
Evaluate data loss against Recovery Point Objective (RPO)
The database was restored from a snapshot taken 10 minutes10\text{ minutes} before outage. Since 10 minutes15 minutes10\text{ minutes} \le 15\text{ minutes}, the RPO target was achieved.
RPO defines the maximum tolerable data loss measured in duration before the disaster occurred.
2
Calculate total downtime duration (RTO + WRT)
Technical system restoration (RTO) took 2.5 hours2.5\text{ hours}. Work Recovery Time (WRT) for reconciliation took 4 hours4\text{ hours}. Total recovery time =2.5 hours+4 hours=6.5 hours= 2.5\text{ hours} + 4\text{ hours} = 6.5\text{ hours}.
Maximum Tolerable Downtime (MTD) encompasses both system restoration and the operational effort required to verify data and return the service to business operation.
3
Compare total recovery duration against Maximum Tolerable Downtime (MTD)
6.5 hours>6 hours6.5\text{ hours} > 6\text{ hours} (MTD). The organization breached its MTD threshold.
Exceeding MTD means business operations experienced impact beyond acceptable tolerances, even though initial technical restoration appeared successful.

Key Concept

Business Continuity Metrics (RPO, RTO, WRT, and MTD)
Question 1637Question

An enterprise security engineer is auditing identity lifecycle management and access control workflows across the organization. Match each operational access activity on the left with its corresponding identity management or AAA (Authentication, Authorization, and Accounting) component on the right.

Click a left item, then click its matching right item

Items

A remote worker enters their user principal name (UPN) into a VPN client login window to claim an identity.
An Identity Provider verifies a user's identity by validating a FIDO2 hardware security key challenge-response.
A network access server checks an Active Directory group membership policy to assign dynamic VLAN permissions to a connected device.
A centralized SIEM ingests RADIUS session logs containing connection start times, total bytes transferred, and disconnect reasons.

Matches

Show answer & explanation

Answer

Entering a UPN maps to Identification; validating FIDO2 credentials maps to Authentication; enforcing dynamic VLAN access rights maps to Authorization; and recording connection metrics and duration maps to Accounting.
Each operational scenario directly aligns with a specific phase in identity and access governance: entering a UPN claims an identity (Identification); verifying FIDO2 credentials proves the claim (Authentication); evaluating group policies to set network privileges grants access boundaries (Authorization); and recording session metrics to SIEM maintains an audit log (Accounting).

Step-by-Step Solution

1
Analyze the first scenario (entering UPN).
Providing a username or UPN asserts a claim of identity without proof.
Identification is the process of presenting an identity claim to a system.
2
Analyze the second scenario (FIDO2 hardware key validation).
Cryptographically verifying the claim proves identity authentic state.
Authentication is the verification step that tests presented credentials.
3
Analyze the third scenario (group membership policy for dynamic VLAN assignment).
Determining privileges and applying access restrictions based on policy.
Authorization determines what rights, permissions, and resources an authenticated identity can access.
4
Analyze the fourth scenario (logging RADIUS connection start/end metrics).
Recording resource consumption and session duration for auditability.
Accounting monitors, tracks, and logs user activity and resource usage.

Key Concept

Authentication, Authorization, and Accounting (AAA) Framework and Identification
Question 1638Question

A security engineer is designing an authentication microservice for an enterprise web application. The security policy requires storing user credentials in a manner that mitigates offline brute-force and precomputed rainbow table attacks if the credential database is compromised. Which of the following cryptographic techniques should the engineer implement to satisfy this requirement?

Show answer & explanation

Answer: Apply a salted key-stretching hashing algorithm with an adjustable work factor.

Answer

Apply a salted key-stretching hashing algorithm with an adjustable work factor.
Applying a salted key-stretching password hashing algorithm (such as Argon2, PBKDF2, or bcrypt) satisfies both requirements. Salting appends a unique random value to each password before hashing to defeat precomputed rainbow tables. Key stretching applies a high work factor through repeated iterations to slow down offline brute-force dictionary attacks.

Step-by-Step Solution

1
Identify the threat vectors described in the scenario.
The requirements explicitly call for protection against precomputed rainbow table attacks and high-speed offline brute-force attacks.
Rainbow table attacks rely on precomputed tables of standard hashes, while brute-force attacks test millions of password combinations per second.
2
Evaluate the cryptographic mechanism required to counter precomputed lookup tables.
Adding a unique random salt to each user password ensures that two identical passwords produce different hashes, rendering precomputed tables ineffective.
Salting forces an attacker to compute a custom lookup table for every individual user salt.
3
Evaluate the cryptographic mechanism required to slow down offline brute-force cracking.
Key-stretching algorithms (such as Argon2, PBKDF2, or bcrypt) execute multiple iterations to artificially increase the computational time required per hash calculation.
Slowing down hash generation significantly increases the time required for an attacker to test candidate passwords.

Key Concept

Salted Key-Stretching Hash Functions for Password Protection
Estimated Time:1m 30s
Question 1639Question

An IT security team is defining operational metric parameters during a Business Impact Analysis (BIA) for an enterprise enterprise resource planning (ERP) environment. Which TWO of the following statements correctly distinguish Recovery Time Objective (RTO) from Recovery Point Objective (RPO)?

Select all that apply

Show answer & explanation

Answer: RTO specifies the maximum acceptable duration of service downtime following a disruptive incident.; RPO specifies the maximum allowable age of unrecovered data or data loss measured in time.

Answer

Recovery Time Objective (RTO) defines the maximum acceptable downtime duration before systems are restored, while Recovery Point Objective (RPO) defines the maximum allowable timeframe of lost data.
The correct statements accurately define Recovery Time Objective (RTO) as the targeted duration of allowable system downtime and Recovery Point Objective (RPO) as the maximum tolerable age of data lost due to a disruptive event. Both parameters are foundational metrics established during a Business Impact Analysis (BIA) to shape continuity and backup strategies.

Step-by-Step Solution

1
Analyze the core definition of Recovery Time Objective (RTO).
RTO is identified as the maximum tolerable duration that a system or business function can remain offline after a disaster.
Establishing RTO guides the selection of disaster recovery methods and restoration speed requirements.
2
Analyze the core definition of Recovery Point Objective (RPO).
RPO is identified as the maximum acceptable window of data loss measured back from the point of failure.
Establishing RPO dictates data backup frequency and replication strategies.
3
Evaluate option statements against RTO and RPO parameters.
Statements defining RTO as downtime duration and RPO as tolerable data loss age accurately represent BIA recovery metrics.
RTO focuses on elapsed operational recovery time, while RPO focuses on data integrity and backup interval currency.

Key Concept

Distinguishing RTO and RPO in Business Impact Analysis
Estimated Time:1m 0s
Question 1640Question

An enterprise security analyst discovers that recent vulnerability scan reports flag several Linux production servers as critical due to missing OS security updates. However, the system administration team provides logs showing that the vendor patches were installed two weeks ago. Further investigation reveals the scanner performed an unauthenticated remote scan relying solely on service banners exposed over open network ports. Which of the following actions should the analyst take to ensure the vulnerability scan accurately reflects the true patch status of the servers?

Show answer & explanation

Answer: Configure credentialed scanning parameters to allow the scanner to verify installed packages directly from the local target operating system.

Answer

Configure credentialed scanning parameters to allow the scanner to verify installed packages directly from the local target operating system.
Unauthenticated vulnerability scans inspect exposed service banners, which frequently causes false positives when backported patches leave version banners unchanged. Configuring credentialed scanning allows the scanner to log into target systems and inspect local package manager records directly, ensuring accurate verification of installed updates.

Step-by-Step Solution

1
Analyze the cause of the reporting mismatch
Unauthenticated network scans rely on banner grabbing, which often reports false positives because patched services may retain their original version banners.
Identifying why the scanner generated inaccurate data is necessary to select the proper technical remediation.
2
Evaluate the capabilities of credentialed scanning
Credentialed scans log directly into the target system to examine local configuration files and package databases.
Authenticating to the host provides accurate data regarding whether patches have been applied.
3
Select the appropriate administrative configuration
Enabling credentialed scanning resolves banner-based false positives without disabling or suppressing scan checks.
This action provides the security team with accurate vulnerability metrics.

Key Concept

Credentialed vs. Unauthenticated Vulnerability Scanning
PreviousPage 82 / 112Next
All practice questions — CompTIA Security+ | Examkin