General Security Concepts

268 questions

Question 81Question

A financial institution upgraded its treasury management software to require biometric verification prior to executing wire transfers, while enforcing role-based policies that constrain transfer limits according to employee job titles. During a post-transaction audit, security analysts confirmed that user identities were successfully verified and authorization boundaries were strictly enforced, but noted that no timestamped system logs were generated to record the specific destination account numbers or transfer amounts modified during sessions. Which pillar of the AAA framework is incomplete in this system design?

Show answer & explanation

Answer: Accounting

Answer

Accounting is the missing AAA pillar because the system fails to maintain timestamped audit logs of user actions and transaction details.
The correct answer is Accounting. The AAA framework consists of Authentication (verifying identity), Authorization (granting permissions), and Accounting (logging activity and auditing). In this scenario, identity verification and role-based privilege enforcement were performed, but recording transaction logs and specific data modifications was omitted, which directly falls under the Accounting pillar.

Step-by-Step Solution

1
Evaluate the first AAA component (Authentication) against the scenario details.
Biometric verification successfully proves the identity of the user initiating the transaction, confirming authentication is present.
Authentication verifies identity before granting access.
2
Evaluate the second AAA component (Authorization) against the scenario details.
Role-based transfer limit enforcement ensures users operate within granted permission bounds, confirming authorization is present.
Authorization controls what resources and actions an authenticated identity can access.
3
Evaluate the third AAA component (Accounting) against the identified operational gap.
The absence of timestamped audit logs detailing modified account numbers and transfer amounts represents a lack of session logging and tracking.
Accounting logs, measures, and audits user activities and resource consumption during active sessions.

Key Concept

Authentication, Authorization, and Accounting (AAA) Framework
Estimated Time:1m 15s
Question 82Question

A security administrator needs to obtain and deploy a new TLS server certificate signed by a public Certificate Authority (CA). What is the correct sequence of administrative steps to accomplish this task?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is: 1) Generate an asymmetric key pair locally on the server; 2) Create a Certificate Signing Request (CSR) containing the public key and domain details; 3) Submit the CSR to the Certificate Authority (CA) for validation and signing; 4) Install the CA-signed digital certificate on the web server.
The standardized PKI certificate enrollment workflow requires local key pair generation first, followed by bundling the public key into a CSR, submitting the CSR to the CA for domain verification and signature, and finally binding the issued certificate to the web service.

Step-by-Step Solution

1
Generate asymmetric key pair on the server
A public key and a protected private key are created.
The server must possess a private key before requesting a corresponding signed certificate.
2
Formulate Certificate Signing Request (CSR)
A CSR file containing the public key and organizational details is generated.
The CA requires the public key and domain identity details to construct the certificate body.
3
Submit CSR to Certificate Authority (CA)
The CA verifies domain control and issues a signed certificate.
Validation establishes trust before the CA applies its digital signature.
4
Install signed certificate on the server
The web server presents the valid CA-signed certificate during TLS handshakes.
Clients can now establish encrypted TLS sessions by verifying the certificate chain back to a trusted root CA.

Key Concept

PKI Certificate Request and Enrollment Lifecycle Workflow
Question 83Question

An organization wants to optimize web traffic performance and protect user privacy by reducing client requests to external Certificate Authorities for certificate status verification. Which of the following PKI mechanisms allows the web server itself to fetch and present a signed, timestamped certificate status directly to the client during the TLS handshake?

Show answer & explanation

Answer: OCSP stapling

Answer

OCSP stapling allows the web server to query the CA and supply a timestamped validation response directly to the client during the TLS handshake.
OCSP stapling allows the web server to query the Online Certificate Status Protocol responder periodically, cache the timestamped signed response, and present it directly to the client during the TLS handshake. This reduces latency and prevents third-party CAs from tracking client IP addresses.

Step-by-Step Solution

1
Identify the performance and privacy requirement
Clients need to verify whether a server's X.509 certificate has been revoked without making distinct outbound HTTP queries to third-party CAs.
Direct client queries to an Online Certificate Status Protocol (OCSP) responder create connection latency and reveal user browsing behavior.
2
Select the PKI feature designed for server-side revocation caching
OCSP stapling offloads OCSP queries to the web server, which periodically retrieves the signed response and appends ('staples') it to the TLS handshake.
This allows clients to verify validity immediately during connection establishment.

Key Concept

OCSP Stapling
Question 84Question

An organization is updating its enterprise access management architecture to align with security frameworks. Match each operational capability on the left to the corresponding pillar or sub-component of the Authentication, Authorization, and Accounting (AAA) framework on the right.

Click a left item, then click its matching right item

Items

Validating user identity claims using a smart card PIN and biometric scanner upon initial workstation sign-in.
Evaluating security group memberships to grant read-only access to specific financial database tables.
Logging session timestamps, bandwidth usage, and administrative CLI command histories to a central SIEM server.
Requesting additional verification factors dynamically when a user attempts access from an unrecognized IP address.

Matches

Show answer & explanation

Answer

Validating user identity via smart card PIN and biometrics maps to Primary Authentication; evaluating group permissions for database access maps to Authorization; logging timestamps, bandwidth, and command histories maps to Accounting; dynamically prompting for extra factors based on location risk maps to Adaptive (Risk-Based) Authentication.
Each item directly aligns with a specific component of the AAA framework. Validating identity via smart card and biometrics is Primary Authentication. Granting or restricting resource access according to permissions is Authorization. Recording session data and command history for forensic audit trail purposes is Accounting. Adjusting authentication steps based on contextual risk indicators (like unfamiliar IP addresses) is Adaptive Authentication.

Step-by-Step Solution

1
Identify the primary function of each scenario item.
Categorize each operational capability according to whether it verifies identity (Authentication), determines privileges (Authorization), or records usage/activity (Accounting).
AAA establishes clear boundaries between verifying who a user is, controlling what they can do, and tracking what they did.
2
Differentiate baseline authentication from dynamic authentication.
Standard multi-factor verification at logon corresponds to Primary Authentication, while contextual step-up verification triggered by anomalous conditions corresponds to Adaptive Authentication.
Adaptive authentication alters identity verification requirements depending on risk signals like unknown network locations.
3
Confirm permission and logging assignments.
Database access rights align with Authorization, and SIEM command/session logs align with Accounting.
Access rights define permissions (authorization), and historical logs provide accountability and auditability (accounting).

Key Concept

Authentication, Authorization, and Accounting (AAA) Framework
Question 85Question

A healthcare organization's cloud operations team plans to update the TLS configuration on its primary API gateways by disabling TLS 1.0 and 1.1 to comply with updated security baselines. Before the Change Advisory Board (CAB) approves this modification, which action should the security team mandate to evaluate the potential security and functional impact of the proposed change?

Show answer & explanation

Answer: Perform an inventory and dependency analysis to identify internal and legacy external systems that rely on older encryption protocols.

Answer

Perform an inventory and dependency analysis to identify internal and legacy external systems that rely on older encryption protocols.
Performing a thorough dependency analysis allows the security and operations teams to identify legacy applications, client software, or third-party services that depend on older TLS versions. Discovering these dependencies before the Change Advisory Board (CAB) approves the request ensures that potential outages are identified early, remediation plans are established, and security impacts are fully understood.

Step-by-Step Solution

1
Evaluate the scope of the proposed infrastructure change.
Disabling legacy cryptographic protocols (TLS 1.0/1.1) affects all incoming client connections that have not updated to modern TLS standards.
Changes to security baselines can break dependent systems if clients rely on deprecated protocol suites.
2
Identify necessary pre-approval change control procedures.
A comprehensive dependency analysis must be conducted to discover legacy integrations, API consumers, and client applications.
Change management policy requires assessing potential operational disruptions and security impacts before CAB approval.
3
Select the option that properly executes a security impact assessment within the formal change control lifecycle.
Conducting an inventory and dependency audit provides empirical risk data to the CAB.
Proactive dependency analysis prevents unexpected service outages and maintains secure operations.

Key Concept

Change Management Security Impact and Dependency Analysis
Question 86Question

A security administrator is configuring a new high-security internal microservice that requires a valid server TLS certificate. Enterprise policy mandates hardware key protection, accurate Subject Alternative Name (SAN) extension mapping, intermediate CA trust anchoring, and OCSP stapling to eliminate direct client queries to the Certificate Authority. In what order should the administrator perform the following steps to deploy the certificate and enable OCSP stapling?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with generating the private key and CSR with SAN attributes, followed by submitting the CSR to the intermediate CA for issuance, installing the server certificate and intermediate CA chain, querying and caching the timestamped OCSP response from the responder, and finally enabling OCSP stapling on the web server.
The proper sequence follows standard PKI lifecycle principles: key generation and CSR creation must precede CA submission and signing. Once the CA returns the signed certificate, installing it along with the intermediate CA chain establishes local service readiness. Next, the server must query the OCSP responder to cache a valid, time-stamped status assertion. Finally, enabling OCSP stapling allows the server to serve this cached status to clients during TLS negotiation.

Step-by-Step Solution

1
Generate key pair and create CSR
A CSR containing the public key and SAN extensions is created, while the private key remains protected in the hardware module.
PKI certificate issuance requires a CSR that includes the public key and identity information before contacting a CA.
2
Submit CSR to Intermediate CA
The CA validates the request, signs the certificate, and returns the signed X.509 certificate.
The CA must sign the public key and SAN details to establish authenticity and issue the valid certificate.
3
Install server certificate and trust chain
The web server is configured with its identity certificate and intermediate CA chain.
The server requires the certificate and full intermediate chain to establish trust with clients during TLS handshakes.
4
Fetch and cache OCSP response
The server securely queries the CA's OCSP responder and receives a signed status payload.
OCSP stapling requires the server itself to periodically contact the OCSP responder and cache the time-stamped proof of validity.
5
Enable OCSP stapling for TLS handshakes
Connecting clients receive the server's OCSP response directly during the TLS handshake.
OCSP stapling delivers the pre-fetched revocation status to the client during negotiation, eliminating client-side CA lookup latency and preserving privacy.

Key Concept

PKI Certificate Enrollment and OCSP Stapling Lifecycle Workflow
Estimated Time:2m 0s
Question 87Question

A security analyst is selecting a key exchange mechanism for lightweight microservices communicating over an untrusted enterprise network. The solution must allow the services to negotiate shared symmetric session keys, ensure that compromise of a long-term private key does not expose past session traffic (perfect forward secrecy), and minimize CPU computational overhead on the constrained nodes. Which of the following algorithms or protocols best fulfills these requirements?

Show answer & explanation

Answer: ECDHE (Elliptic Curve Diffie-Hellman Ephemeral)

Answer

ECDHE (Elliptic Curve Diffie-Hellman Ephemeral) is the correct choice because it enables key agreement with perfect forward secrecy using lower computational overhead than traditional asymmetric methods.
ECDHE (Elliptic Curve Diffie-Hellman Ephemeral) uses temporary, ephemeral keys generated for each session to ensure perfect forward secrecy. Because it uses elliptic curve cryptography, it requires substantially less processing power and memory than traditional finite-field Diffie-Hellman or static RSA.

Step-by-Step Solution

1
Identify the primary cryptographic requirement
The scenario requires key exchange with perfect forward secrecy (PFS) and high computational efficiency.
Session keys must be dynamically negotiated without relying on static long-term private keys for decryption.
2
Evaluate key agreement protocols against constraints
Diffie-Hellman with ephemeral keys (DHE) provides PFS. Adding Elliptic Curve Cryptography (ECDHE) reduces resource consumption.
ECC achieves equivalent key strength with significantly shorter key lengths compared to standard Diffie-Hellman or RSA.
3
Eliminate non-key-exchange mechanisms
Discard symmetric ciphers (AES-GCM) and hash authentication mechanisms (HMAC) as they do not perform key negotiation.
Selecting symmetric ciphers or hashes mistakes bulk data protection for key establishment protocols.

Key Concept

Diffie-Hellman Ephemeral and Perfect Forward Secrecy
Question 88Question

An enterprise security operations team needs to update core firewall access control lists (ACLs) to accommodate a new external application service. Place the standard security change management workflow steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for the change control workflow is: 1) Perform security impact analysis and document backout plan, 2) Submit change request to CAB for authorization, 3) Validate changes in a staging environment, 4) Implement changes in production during authorized window, and 5) Conduct post-implementation review.
A structured change management workflow ensures security oversight by requiring initial risk assessment and backout planning, CAB authorization, pre-deployment staging validation, scheduled production execution, and final post-implementation verification.

Step-by-Step Solution

1
Analyze security impact and draft change documentation.
A clear scope, security assessment, and rollback strategy are documented.
Change management policy requires thorough risk assessment before seeking organizational approval.
2
Submit proposal for CAB review.
The Change Advisory Board evaluates business risk and approves implementation.
Formal authorization ensures change alignment with organizational risk tolerance and operational schedules.
3
Execute testing in staging environment.
The proposed rule set and backout steps are validated as safe and functional.
Pre-production testing prevents unexpected outages or unintended security exposure on live networks.
4
Deploy modifications into production.
Firewall ACL updates are applied during the scheduled change window.
Execution within maintenance windows minimizes business disruption during system updates.
5
Perform post-implementation review.
Production security baselines are audited and the change ticket is closed.
Post-implementation audit confirms successful deployment and verifies no drift from baseline security requirements.

Key Concept

Formal Change Management Workflow and Security Impact Lifecycle
Question 89Question

A security administrator is evaluating mechanisms to verify whether a digital certificate has been invalidated before its natural expiration date. Which of the following methods can be used to check the revocation status of an enterprise TLS certificate? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Querying an Online Certificate Status Protocol (OCSP) responder for real-time validation; Downloading a Certificate Revocation List (CRL) published by the issuing CA

Answer

The revocation status of a digital certificate can be checked using Online Certificate Status Protocol (OCSP) queries and Certificate Revocation Lists (CRLs).
Online Certificate Status Protocol (OCSP) queries provide a real-time method to check certificate status with a responder, while Certificate Revocation Lists (CRLs) provide a published list of revoked certificate serial numbers by the CA. Both are standard mechanisms designed specifically to verify revocation status.

Step-by-Step Solution

1
Identify the goal of checking if a certificate was revoked prior to expiration.
Recognize that PKI provides specific revocation checking mechanisms maintained by or linked to the issuing CA.
Certificates can be compromised or superseded before their validity period ends.
2
Evaluate standard PKI revocation mechanisms.
Identify Online Certificate Status Protocol (OCSP) for real-time status checks and Certificate Revocation Lists (CRLs) for downloadable lists of revoked certificate serial numbers.
Both protocols exist specifically to communicate revocation status from the CA to relying parties.

Key Concept

Certificate Revocation Validation (CRL and OCSP)
Estimated Time:45s
Question 90Question

An enterprise security engineer configures a centralized TACACS+ server to manage administrative access to core switches. A network technician successfully enters their credentials and time-based one-time password (TOTP) to establish an interactive console session. However, when attempting to execute interface configuration commands, the router rejects the command with a privilege denial message. Which pillar of the AAA framework is responsible for determining whether the technician can execute these specific commands?

Show answer & explanation

Answer: Authorization

Answer

Authorization is the AAA pillar responsible for validating and granting specific privilege levels and command permissions to an identified user.
Authorization is the AAA component that determines the specific actions, resources, and commands an authenticated user is permitted to access. In this scenario, while authentication succeeded at login, authorization policies restricted the user from executing privileged configuration commands.

Step-by-Step Solution

1
Analyze the initial logon phase in the scenario.
The technician successfully provided a username, password, and TOTP to establish identity.
This confirms that the Authentication pillar successfully verified who the technician is.
2
Evaluate the cause of the command execution failure.
The system denied access when specific configuration commands were entered.
Permissions and command-level access privileges are governed by policy enforcement within Authorization.
3
Identify the corresponding AAA pillar.
Authorization governs command-level restrictions in protocols such as TACACS+.
Per-command privilege checking is the explicit function of Authorization.

Key Concept

Authentication, Authorization, and Accounting (AAA) Functional Roles
Estimated Time:1m 0s
Question 91Question

A security administrator is deploying a centralized access management solution for enterprise network infrastructure. Which of the following technical configurations directly represent the Authorization pillar of the AAA framework? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Assigning Cisco privilege level 15 permissions to network engineers upon session establishment on core routers.; Applying security group policies that restrict database backup accounts to read-only permissions on storage volumes.

Answer

The configurations representing Authorization are assigning privilege level 15 permissions to network engineers on core routers and applying security group policies that restrict backup accounts to read-only permissions on storage volumes.
Authorization specifies rights, privileges, and access levels granted to an entity. Assigning router privilege levels determines which commands an administrator can execute, and applying security group policy restrictions limits account rights on storage volumes. Both actions directly define and enforce access rights.

Step-by-Step Solution

1
Analyze each option against the core definitions of AAA (Authentication, Authorization, and Accounting).
Identify whether the configuration verifies identity (Authentication), defines permissions/access rights (Authorization), or records user activity/events (Accounting).
AAA components separate identity proof, permission assignment, and event logging into distinct operational pillars.
2
Evaluate privilege assignment and policy restriction controls.
Determined that assigning router privilege levels and restricting storage volume access to read-only explicitly control permissions.
Authorization enforces access boundaries and determines what an authenticated subject is allowed to do.
3
Evaluate credential verification and audit logging controls.
Determined that smart card PIN validation is authentication, and CLI command history logging is accounting.
Credential validation proves identity, while command logging records activity for compliance and forensic tracking.

Key Concept

Authentication, Authorization, and Accounting (AAA)
Question 92Question

A DevOps engineering team plans to deploy an automated continuous integration and continuous deployment (CI/CD) pipeline update that alters how production application secrets are fetched and stored. To minimize potential security impacts and align with enterprise change management governance, which of the following procedures should be completed before deploying this change to production? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Perform a security impact analysis and test the new secret management workflow within an isolated staging environment.; Obtain approval from the Change Advisory Board (CAB) following a documented evaluation of the rollback strategy.

Answer

Prior to deploying a CI/CD pipeline change affecting application secrets to production, the team must evaluate the security impact in a staging environment and obtain CAB authorization alongside a validated rollback plan.
Proper change control requires validating security impacts in non-production environments and obtaining formal approval from governance bodies like the Change Advisory Board (CAB) supported by a verified rollback plan. This ensures both operational continuity and security posture preservation.

Step-by-Step Solution

1
Identify key requirements of enterprise change management
Recognize that change management requires testing security impacts in staging and securing formal approval before production release.
Deploying untested changes to production or bypassing change control increases operational and security risk.
2
Evaluate the correct operational and governance controls
Selecting staging environment security testing and CAB review with a documented rollback plan satisfies both security analysis and administrative compliance.
CAB review verifies risk exposure, while staging validation ensures secret isolation mechanisms function without breaking dependent services.
3
Eliminate inappropriate control actions and ineffective mitigations
Discard option suggesting control reclassification and option relying on external WAF rules to fix internal software flaws.
Reclassifying control types does not mitigate risk, and network perimeter controls cannot remediate application-level credential handling flaws.

Key Concept

Change Management Workflows and Security Impact Assessments
Question 93Question

An organization is preparing to decommission a legacy Lightweight Directory Access Protocol (LDAP) directory server following a enterprise-wide migration to a cloud identity provider. To ensure business continuity and prevent unexpected service disruptions during the shutdown, which of the following actions should the security team perform FIRST to evaluate the security impact of this change?

Show answer & explanation

Answer: Perform a dependency analysis and review directory authentication logs to identify any remaining applications or devices reliant on the legacy service.

Answer

Perform a dependency analysis and review directory authentication logs to identify any remaining applications or devices reliant on the legacy service.
Prior to decommissioning core security or identity infrastructure, change management best practices require conducting a thorough dependency analysis and reviewing system logs. This proactive assessment identifies legacy applications, service accounts, or hardware devices still utilizing the service, allowing administrators to migrate them safely without causing unexpected outages.

Step-by-Step Solution

1
Identify the primary operational and security risk associated with decommissioning critical identity infrastructure.
Undocumented service dependencies could cause critical application outages or fallbacks to insecure authentication methods.
Decommissioning systems requires discovering all integrated components before removing service availability.
2
Evaluate the initial step of a change management security impact assessment.
Reviewing active authentication logs and service configuration references provides empirical evidence of usage.
Empirical log analysis reveals real-time usage patterns that static documentation may omit.
3
Determine the proper sequence prior to change approval and execution.
Performing dependency mapping ensures comprehensive risk mitigation before submitting final change approval requests.
Proactive dependency discovery ensures controlled, risk-aware infrastructure modification.

Key Concept

Dependency mapping and risk analysis in change management workflows
Question 94Question

A security administrator is configuring a secure transmission channel for automated database synchronization between two enterprise data centers. The organization requires a cryptographic configuration that guarantees mutual identity authentication of both endpoint servers, session confidentiality with perfect forward secrecy (PFS), and payload integrity. Which of the following cryptographic mechanisms or protocols should the administrator select? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) key exchange during TLS session negotiation; Enforce Mutual TLS (mTLS) with dual-sided X.509 digital certificate validation

Answer

The correct cryptographic mechanisms to implement are Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) key exchange for perfect forward secrecy and Mutual TLS (mTLS) with X.509 certificates for mutual authentication.
Implementing Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) key exchange provides dynamic, single-session keys that guarantee perfect forward secrecy. Pairing ECDHE with Mutual TLS (mTLS) ensures both database servers authenticate each other's identity using digital certificates prior to payload transmission.

Step-by-Step Solution

1
Evaluate the requirement for session confidentiality with perfect forward secrecy (PFS).
Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) generates temporary, single-session key pairs for each connection, ensuring past traffic remains secure even if long-term private keys are exposed.
Ephemeral Diffie-Hellman variants are necessary to fulfill PFS constraints.
2
Evaluate the requirement for mutual authentication between enterprise data center nodes.
Mutual TLS (mTLS) requires both the initiating server and receiving server to present X.509 certificates issued by a trusted Certificate Authority.
Standard TLS only authenticates the server to the client, whereas mTLS enforces bidirectional certificate verification.
3
Analyze and eliminate unsuitable cryptographic choices.
Static RSA key exchange lacks PFS, RSA asymmetric encryption is unsuitable for bulk data transfers due to performance overhead, and MD5 is cryptographically broken.
Cryptographic implementations must align cipher capabilities with specific operational performance and risk requirements.

Key Concept

Key Exchange Mechanisms and Authentication Protocols
Estimated Time:1m 30s
Question 95Question

An enterprise security team is upgrading its internal 802.1X EAP-TLS network authentication infrastructure. During validation testing, corporate endpoints fail to establish a TLS tunnel with the RADIUS server, returning certificate trust and capability errors. Further inspection confirms that the root and subordinate Intermediate CA certificates are properly installed in the endpoint trust stores. Which of the following certificate misconfigurations would cause endpoints to reject the RADIUS server certificate? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The certificate lacks an Extended Key Usage (EKU) extension explicitly defining Server Authentication.; The certificate omits the Subject Alternative Name (SAN) extension, relying solely on the Subject Common Name (CN) field.

Answer

The authentication failures are caused by omitting the Extended Key Usage (EKU) extension specifying Server Authentication and omitting the Subject Alternative Name (SAN) extension required for modern hostname and identity validation.
For an 802.1X EAP-TLS authentication server certificate to be validated successfully by endpoints, it must contain specific X.509 v3 extensions. First, the Extended Key Usage (EKU) field must explicitly specify Server Authentication so client supplicants verify the certificate's intended operational role. Second, modern clients strictly enforce RFC 6125 standards and require the Subject Alternative Name (SAN) extension to match server identity attributes. Omitting either extension leads to validation failure despite having trusted root and intermediate certificates.

Step-by-Step Solution

1
Analyze X.509 v3 extension constraints required for 802.1X EAP-TLS server certificates.
Identified that Extended Key Usage (EKU) must explicitly state Server Authentication (OID 1.3.6.1.5.5.7.3.1) so supplicants accept the server's intended role.
Without the Server Authentication EKU attribute, supplicant validation engines treat the certificate as invalid for establishing TLS server connections.
2
Evaluate domain identity matching rules implemented in modern operating system supplicants.
Identified that modern validation enforcement requires the Subject Alternative Name (SAN) extension.
RFC 6125 deprecates using only the Subject Common Name (CN) for name validation, causing endpoints to reject server certificates that do not include the SAN extension.

Key Concept

X.509 v3 Extension Attributes and Endpoint Validation Rules
Question 96Question

A security administrator is setting up an automated deployment server that requires an enterprise-issued code-signing certificate from an internal Certificate Authority (CA). Which of the following procedures correctly follows Public Key Infrastructure (PKI) standards for generating and submitting a Certificate Signing Request (CSR)?

Show answer & explanation

Answer: Generate the public and private key pair locally on the deployment server, protect the private key on that server, and transmit only the CSR containing the public key to the CA for signing.

Answer

Generate the public and private key pair locally on the deployment server, protect the private key on that server, and transmit only the CSR containing the public key to the CA for signing.
In standard PKI workflows, the applicant system generates its own public/private key pair locally. The private key is securely retained, and only the public key along with identification data is packaged into the Certificate Signing Request (CSR) sent to the Certificate Authority. This prevents private key exposure during transmission.

Step-by-Step Solution

1
Analyze standard PKI key pair generation location
The target system (deployment server) generates the asymmetric key pair locally so the private key never leaves the boundary of the requesting system.
Preventing private key transit across network interfaces minimizes key exposure and compromise risk.
2
Evaluate the contents and submission of the Certificate Signing Request (CSR)
The CSR package includes the subject identity details and the generated public key, digitally signed by the generated private key to prove key ownership.
The CA requires only the public key and identity validation to issue a signed X.509 digital certificate.
3
Select the choice matching correct CSR generation workflow
The option specifying local key generation and transmitting only the CSR with the public key to the CA is identified as the correct procedure.
This maintains appropriate security boundaries and adheres to standard PKI lifecycle rules.

Key Concept

Public Key Infrastructure (PKI) Certificate Signing Request (CSR) Lifecycle Workflow
Question 97Question

A DevOps security engineer configures a CI/CD build pipeline to publish container images to a private registry. The registry uses mutual TLS (mTLS) to verify the build agent's identity and evaluates microservice access control lists (ACLs) to ensure the agent holds write permissions. However, an internal audit reveals that detailed logs of image tag modifications and timestamped service upload events are not being recorded or stored centrally. Which pillar of the AAA security framework is absent in this implementation?

Show answer & explanation

Answer: Accounting

Answer

Accounting is the pillar of the AAA security framework missing from this deployment.
Accounting is responsible for tracking user and service activities, recording event metrics, and maintaining centralized audit trails. The failure to record image uploads and timestamped modifications directly indicates that Accounting is missing.

Step-by-Step Solution

1
Analyze the active security components described in the scenario.
Mutual TLS (mTLS) validates system identity (Authentication) and ACLs restrict write actions (Authorization).
Identifying existing controls determines which components of AAA are already present.
2
Determine the unaddressed operational requirement.
The system fails to log timestamped upload events and configuration modifications centrally.
Identifying the gap isolates the unfulfilled security function.
3
Map the missing capability to AAA framework pillars.
Logging, monitoring, and audit logging correspond to Accounting.
Accounting specifically covers tracking activity and maintaining audit trails.

Key Concept

Authentication, Authorization, and Accounting (AAA)
Estimated Time:1m 15s
Question 98Question

An enterprise security architect is reviewing access control operations across different corporate infrastructure components. Match each operational scenario on the left with its corresponding Authentication, Authorization, or Accounting (AAA) functional role on the right.

Click a left item, then click its matching right item

Items

A RADIUS server validates an employee's EAP-TLS digital certificate to verify identity before granting entry to the corporate network.
A firewall engine checks security group rules to grant or block an authenticated user's access to the production database subnet.
A TACACS+ server records the exact CLI commands executed by a network administrator during a switch maintenance window.
A gateway logging engine tracks session duration, bandwidth utilization, and IP addresses for remote access VPN connections.

Matches

Show answer & explanation

Answer

EAP-TLS certificate validation matches Authentication; checking firewall rules for subnet access matches Authorization; logging specific switch CLI commands matches Accounting (Action Auditing); tracking VPN bandwidth and session duration matches Accounting (Resource Tracking).
Authentication verifies identity through credentials such as digital certificates. Authorization enforces policies that determine what actions an authenticated entity can perform. Accounting logs both explicit administrative actions for auditability and general session metrics for resource tracking.

Step-by-Step Solution

1
Identify scenarios that verify identity credentials.
Scenario 1 proves identity via certificate verification, which corresponds to Authentication.
Authentication is strictly concerned with establishing and verifying identity.
2
Identify scenarios that enforce access permissions or policies.
Scenario 2 checks rule sets to allow or deny network transport paths, which corresponds to Authorization.
Authorization evaluates permissions after identity has been established.
3
Differentiate between action auditing and resource tracking within Accounting scenarios.
Scenario 3 logs specific executed commands (Action Auditing), while Scenario 4 captures metrics like bandwidth and connection time (Resource Tracking).
Accounting encompasses both non-repudiable activity auditing and quantitative resource consumption logging.

Key Concept

Authentication, Authorization, and Accounting (AAA) functional pillars
Question 99Question

An enterprise security team needs to deploy an urgent software patch to core payment gateways to remediate an actively exploited remote code execution vulnerability. To balance immediate threat mitigation with enterprise governance and risk management requirements, which of the following actions should the team take FIRST according to formal change management principles?

Show answer & explanation

Answer: Submit an emergency change request to the Emergency Change Advisory Board for expedited authorization with a documented backout procedure.

Answer

The team should submit an emergency change request to the Emergency Change Advisory Board (eCAB) for expedited authorization with a documented backout procedure.
Emergency Change Management procedures exist to handle urgent situations like zero-day vulnerability mitigation. Submitting an emergency change request to an Emergency Change Advisory Board allows for expedited evaluation of security impact and risk, while ensuring a backout plan is established to protect operational continuity.

Step-by-Step Solution

1
Evaluate the context of the change
Identified as a critical vulnerability requiring rapid mitigation without skipping governance
Emergency patches address active threats that cannot wait for standard change review cycles.
2
Select the correct change control path
Choose the Emergency Change Advisory Board (eCAB) process
The emergency change workflow provides expedited review and risk assessment designed specifically for urgent security fixes.
3
Ensure essential safety mechanisms are included
Attach a rollback/backout plan and conduct basic risk verification
Even under emergency conditions, a rollback plan prevents extended downtime if the patch causes unexpected failure.

Key Concept

Emergency Change Control and Security Impact Assessment
Question 100Question

An enterprise security architect is establishing a two-tier internal Public Key Infrastructure (PKI) hierarchy. The Root CA will remain air-gapped to maintain security, while a new Intermediate CA will issue operational certificates to web servers. Place the administrative steps for provisioning and activating the Intermediate CA into the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct administrative order is to first generate the private key and CSR locally on the Intermediate CA, transport the CSR out-of-band to the air-gapped Root CA, sign the request with the Root CA's private key, and finally import the signed intermediate certificate into the Intermediate CA while publishing the Root CA public certificate to the enterprise trust store.
In a standard two-tier PKI hierarchy with an air-gapped Root CA, the Intermediate CA first generates its own private key and CSR locally. The request is transported out-of-band to the Root CA, which signs the request using its private key. Finally, the signed certificate is installed on the Intermediate CA, and the Root CA's public certificate is deployed to endpoints' trusted root store to establish a valid trust chain.

Step-by-Step Solution

1
Generate private key pair and CSR locally on the Intermediate CA server
Creates the asymmetric key pair and formats the public key with subject identity into a CSR.
Private keys must be generated on the host system to prevent key compromise during transit.
2
Transport the CSR to the Root CA via offline media
Delivers the signing request to the isolated issuing system.
Air-gapped Root CAs lack network connectivity to defend against remote network attacks.
3
Sign the Intermediate CSR using the Root CA's private key
Generates a digitally signed Intermediate CA certificate containing path length basic constraints.
The Root CA acts as the trust anchor that validates and authorizes the Intermediate CA.
4
Install the signed certificate on the Intermediate CA and publish the Root CA certificate to client trust stores
Enables the Intermediate CA to sign leaf certificates and ensures endpoints can validate the full certificate path back to the Root CA.
Clients must possess the Root CA's public certificate in their trusted root store to build a trusted certificate path.

Key Concept

Two-tier PKI deployment and Intermediate CA certificate signing workflow
PreviousPage 5 / 14Next
General Security Concepts Practice Questions — CompTIA Security+ — Page 5 | Examkin