General Security Concepts

268 questions

Question 161Question

An enterprise organization is transitioning from a legacy remote-access VPN infrastructure to a Zero Trust Architecture (ZTA). During the redesign, a security architect must define how access requests to sensitive corporate applications are evaluated by the Policy Engine and Policy Enforcement Point. Which of the following operational practices best aligns with the core Zero Trust principle of explicit validation and continuous verification?

Show answer & explanation

Answer: Evaluating user identity, device health, and environmental context dynamically for every individual resource access request regardless of network position

Answer

Evaluating user identity, device health, and environmental context dynamically for every individual resource access request regardless of network position
The correct response highlights the core pillar of Zero Trust Architecture: inspecting and validating every request individually using identity, device security posture, and runtime context. It eliminates implicit perimeter trust entirely.

Step-by-Step Solution

1
Identify core Zero Trust Architecture (ZTA) principles
ZTA relies on 'never trust, always verify', enforcing continuous verification, explicit validation, and least privilege.
Legacy perimeter security assumes internal traffic is trusted, whereas Zero Trust treats all networks and requests as untrusted.
2
Analyze how the Policy Engine (PE) and Policy Enforcement Point (PEP) operate
The Policy Engine evaluates context (user status, device integrity, location) and decides whether to grant access, while the PEP enforces this decision per request.
Continuous verification requires evaluating every request dynamically rather than relying on one-time authentication.
3
Select the option that correctly embodies dynamic, request-level verification
Evaluating user identity, device posture, and context dynamically per request regardless of location represents true Zero Trust implementation.
This meets the requirement of explicit validation across both control plane decisions and data plane enforcement.

Key Concept

Zero Trust Architecture Principles (Continuous Verification and Explicit Validation)
Question 162Question

A financial enterprise operates a microservices environment governed by Zero Trust Architecture (ZTA) principles. A remote system administrator successfully completes multi-factor authentication (MFA) from a corporate-managed endpoint. Ten minutes into the session, the endpoint's telemetry indicates that its local endpoint detection and response (EDR) agent has been disabled, and the connection origin dynamically shifts to an unknown unmanaged network. Which of the following actions best demonstrates the principle of continuous verification in this scenario?

Show answer & explanation

Answer: The Policy Engine dynamically re-evaluates session risk signals and instructs the Policy Administrator to terminate session access or request step-up posture validation despite prior authentication.

Answer

The correct answer states that the Policy Engine dynamically re-evaluates session risk signals and instructs the Policy Administrator to terminate session access or request step-up posture validation despite prior authentication.
Zero Trust Architecture mandates continuous verification and explicit validation. Initial multi-factor authentication does not grant persistent trust. When contextual factors change during an active session (such as EDR agent disabling or IP address changes), the Policy Engine must immediately re-assess threat signals and direct the Policy Administrator to modify, step-up, or terminate access privileges.

Step-by-Step Solution

1
Analyze the state change presented in the enterprise scenario under NIST SP 800-207 Zero Trust guidelines.
Identified that although initial authentication succeeded, post-login environmental context (EDR disabled, network location changed) degraded device trustworthiness.
Zero Trust mandates that access decisions are dynamic and continuous throughout the entirety of every transaction.
2
Determine the functional roles of Zero Trust logical components (Policy Engine, Policy Administrator, Policy Enforcement Point).
The Policy Engine evaluates threat context and security posture to render access decisions, instructing the Policy Administrator to update enforcement rules at the Policy Enforcement Point.
Continuous verification requires real-time telemetry processing and dynamic policy enforcement across active network connections.

Key Concept

Zero Trust Architecture Principles - Continuous Verification and Dynamic Authorization
Question 163Question

A financial enterprise is upgrading its automated clearing house payment processing system. To prevent fraud, the system requires that submitted wire transfers include a cryptographic control. The lead security architect proposes requiring sender applications to sign transfer payloads using an asymmetric private key rather than generating a Hash-based Message Authentication Code (HMAC) with a pre-shared symmetric key. Which security objective is uniquely satisfied by transitioning to the asymmetric digital signature approach?

Show answer & explanation

Answer: Non-repudiation, because any relying third party can independently verify the sender's identity using their public key, preventing the sender from denying transmission.

Answer

Non-repudiation, because any relying third party can independently verify the sender's identity using their public key, preventing the sender from denying transmission.
Asymmetric digital signatures provide non-repudiation because the signing operation uses a unique private key known only to the sender. Anyone with access to the sender's public key can verify the signature's authenticity. Because HMACs use a shared symmetric key, both sender and receiver possess the ability to calculate the message authentication code, preventing either party from mathematically proving to an outside auditor who originated the payload.

Step-by-Step Solution

1
Analyze the cryptographic properties of HMAC vs asymmetric digital signatures.
HMAC relies on a symmetric pre-shared key shared between endpoints. Asymmetric signatures use a private key for signing and a public key for verification.
Understanding key distribution distinguishes bilateral trust from third-party verifiable trust.
2
Evaluate which CIA triad pillar or related property is missing in shared-key HMAC operations.
Because both sender and receiver hold the identical shared secret key in HMAC operations, either party could technically generate a valid HMAC tag. Thus, neither party can prove to an independent third party which entity produced the message.
Non-repudiation requires proof of origin that cannot be forged by the recipient or other key holders.
3
Identify the security objective uniquely met by asymmetric digital signing.
Since only the sender possesses the private signing key, and any auditor or receiver can verify it using the public key, the sender cannot repudiate (deny) sending the payload.
This establishes non-repudiation.

Key Concept

Non-Repudiation vs. Integrity in Cryptographic Controls
Question 164Question

An enterprise cloud engineering team is establishing baseline security controls for a newly migrated production environment. Match each technical implementation on the left with the primary security pillar or objective it satisfies on the right.

Click a left item, then click its matching right item

Items

Applying asymmetric digital signatures to automated infrastructure deployment manifests before execution
Configuring SHA-256 cryptographic checksums coupled with write-once-read-many (WORM) audit logging
Deploying active-active multi-region database replicas with automated health-check failover
Enforcing client-side AES-256-GCM encryption on cloud object storage buckets

Matches

Show answer & explanation

Answer

Asymmetric digital signatures map to Non-Repudiation; SHA-256 hashing with WORM storage maps to Integrity; Active-active multi-region redundancy maps to Availability; Client-side AES-256 encryption maps to Confidentiality.
Each control satisfies its corresponding pillar: asymmetric digital signatures cryptographically bind identity to deployment actions for non-repudiation; SHA-256 hashing with WORM prevents undetected log alteration for integrity; multi-region active-active clustering maintains service uptime for availability; client-side AES-256 encryption prevents unauthorized data viewing for confidentiality.

Step-by-Step Solution

1
Analyze the technical control for proof of origin and author identity.
Asymmetric digital signatures tie deployment actions directly to the signer's private key, establishing non-repudiation.
Non-repudiation ensures an individual or system cannot deny having performed a specific transaction or authorization.
2
Evaluate controls designed to prevent or detect unauthorized data modification.
SHA-256 hashing combined with WORM storage preserves audit records against undetected changes, fulfilling integrity.
Integrity guarantees data accuracy, completeness, and protection against unauthorized modification.
3
Examine operational controls implemented for uptime and disaster recovery.
Multi-region active-active database clustering ensures resources remain accessible during hardware or network failures, maintaining availability.
Availability ensures systems and data are operational and accessible to authorized users whenever needed.
4
Identify controls designed to prevent unauthorized disclosure of stored data.
Client-side AES-256-GCM encryption secures payload data from unauthorized exposure, guaranteeing confidentiality.
Confidentiality protects sensitive data from unauthorized access or disclosure.

Key Concept

CIA Triad and Non-Repudiation
Question 165Question

A security analyst configures an automated reporting tool to sign all generated financial reports using an asymmetric private key. Which of the following core security objectives are directly provided by using digital signatures in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Integrity; Non-repudiation

Answer

The core security objectives directly provided by digital signatures are Integrity and Non-repudiation.
Digital signatures provide integrity by allowing recipients to detect document modification through cryptographic hashing, and non-repudiation by binding the signature uniquely to the sender's private key.

Step-by-Step Solution

1
Identify the cryptographic mechanism described in the scenario.
The scenario uses asymmetric digital signatures applied to financial reports.
Determining the security control type is necessary to evaluate which security pillars it fulfills.
2
Evaluate how digital signatures affect data tampering.
A cryptographic hash verified by the signature ensures the data has not been altered in transit or storage.
This satisfies the requirement for integrity.
3
Evaluate how asymmetric keys establish proof of origin.
Because the signing key is private to the origin, the sender cannot plausibly deny signing the message.
This satisfies the requirement for non-repudiation.

Key Concept

Digital signatures combine hashing and asymmetric cryptography to guarantee integrity and non-repudiation without encrypting the underlying data for confidentiality.
Question 166Question

A security analyst deploys an intentionally vulnerable decoy server on an isolated network segment. The server contains simulated sensitive files and fake credentials designed to attract threat actors, observe their tactics, and generate alerts upon any interaction. Which of the following deception technologies has the analyst implemented?

Show answer & explanation

Answer: Honeypot

Answer

Honeypot
A honeypot is a deception mechanism designed to act as a decoy to lure attackers away from critical production resources while collecting telemetry on unauthorized techniques and behaviors.

Step-by-Step Solution

1
Identify the primary operational goal described in the scenario.
The goal is to lure threat actors using an intentionally vulnerable decoy server to observe tactics and alert on unauthorized interaction.
Deception technologies create false targets to draw malicious activity away from production systems.
2
Compare the scenario characteristics against standard security technology definitions.
A decoy system containing dummy data deployed specifically for monitoring adversary activity is defined as a honeypot.
Honeypots have no legitimate production value; any interaction with them is treated as suspicious or malicious activity.

Key Concept

Deception and Disruption Technologies
Question 167Question

A healthcare provider is deploying a tele-radiology platform where remote radiologists submit diagnostic reports to hospital electronic health record (EHR) systems. Security policy dictates that the platform must guarantee two key objectives: (1) hospitals must be able to prove which specific radiologist authored a report such that the radiologist cannot later claim they did not send it, and (2) any alteration to report contents during transit or storage must be immediately detectable. Which of the following technical controls must be implemented to fulfill these security requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Digital signatures applied to diagnostic reports using each radiologist's private key; Cryptographic hashing generated for report payloads prior to transmission

Answer

The organization must implement digital signatures applied with individual private keys (to provide non-repudiation and integrity) and cryptographic hashing of report payloads (to verify data integrity).
Digital signatures created with asymmetric private keys provide non-repudiation by binding the specific sender's identity to the report, while cryptographic hashing generates verification digests that detect any file alterations to preserve integrity.

Step-by-Step Solution

1
Analyze Requirement 1: Non-repudiation of authorship
Non-repudiation requires a mechanism where the sender's identity is cryptographically bound to the data using a secret known only to the sender (a private key). Digital signatures fulfill non-repudiation because only the private key owner could have produced the signature.
Symmetric shared keys or standard login permissions cannot prove individual authorship since keys/credentials may be shared or managed centrally.
2
Analyze Requirement 2: Detection of unauthorized modifications (Integrity)
Data integrity is verified using cryptographic hash functions (such as SHA-256) or digital signatures. Comparing the computed hash digest against the expected hash reveals any tampering in transit or storage.
Hashing creates a deterministic value unique to the exact byte sequence of the diagnostic file.
3
Evaluate distractors against CIA and Non-Repudiation concepts
Symmetric encryption with a shared key ensures confidentiality but fails non-repudiation. RBAC enforces authorization permissions but cannot cryptographically prove data integrity or origin.
Confidentiality and authorization address different security pillars than non-repudiation and integrity.

Key Concept

CIA Triad and Non-Repudiation
Question 168Question

A security architect is establishing control and data plane boundaries for a microsegmented enterprise network undergoing transition to a Zero Trust Architecture (ZTA). Match each logical Zero Trust component with its corresponding operational role during access evaluations.

Click a left item, then click its matching right item

Items

Policy Engine (PE)
Policy Administrator (PA)
Policy Enforcement Point (PEP)

Matches

Show answer & explanation

Answer

The Policy Engine evaluates policies to make access decisions; the Policy Administrator communicates commands to establish/terminate communication channels; and the Policy Enforcement Point directly intercepts traffic and enforces policies at the data plane.
The Policy Engine evaluates context and policy rules to output access decisions. The Policy Administrator receives those decisions and manages credentials or signaling to setup/tear down communication paths. The Policy Enforcement Point intercepts connections directly to enforce policy controls on active network sessions.

Step-by-Step Solution

1
Identify the primary decision-making core of Zero Trust Architecture.
Recognize that the Policy Engine (PE) compares access requests against defined security policies to make grant/deny decisions.
Separation of control plane logic requires a centralized decision authority.
2
Identify the component responsible for signaling and connection management.
Recognize that the Policy Administrator (PA) executes PE decisions by instructing the control plane to open or close sessions.
The PA acts as the mediator between logical decisions and physical connection establishment.
3
Identify the data plane component handling direct traffic flow.
Recognize that the Policy Enforcement Point (PEP) resides on the data plane to physically allow, monitor, or block traffic.
PEPs act as gatekeepers directly in the flow of traffic.

Key Concept

Zero Trust Control Plane vs. Data Plane Architecture Components (NIST SP 800-207)
Question 169Question

A security analyst is reviewing access policies during an initiative to adopt a Zero Trust Architecture (ZTA). The analyst needs to ensure that access decisions are never granted solely based on a device's physical or network location. Which core Zero Trust principle directly addresses this requirement?

Show answer & explanation

Answer: Explicit verification of identity, context, and security posture for every access request

Answer

Explicit verification of identity, context, and security posture for every access request
Explicit verification mandates that all access requests are authenticated, authorized, and validated against dynamic contextual policies regardless of where the request originates.

Step-by-Step Solution

1
Identify the primary requirement in the scenario
The scenario requires eliminating automatic trust based on network or physical location.
Zero Trust assumes that threats exist both inside and outside the traditional enterprise perimeter.
2
Evaluate Zero Trust principles against the requirement
Explicit verification requires dynamic authentication and authorization for every access attempt using contextual data.
This guarantees that simply residing on an internal network segment does not grant implicit access to resources.

Key Concept

Zero Trust Architecture Principles - Explicit Verification
Estimated Time:45s
Question 170Question

An enterprise security manager needs to ensure that high-priority system change requests sent via email cannot be denied by the author after submission. Which of the following security concepts specifically addresses this requirement?

Show answer & explanation

Answer: Non-repudiation

Answer

Non-repudiation
Non-repudiation provides proof of origin and integrity, ensuring that a party to a transaction or communication cannot deny sending a message.

Step-by-Step Solution

1
Analyze the scenario requirement
The requirement focuses on preventing an author from denying that they submitted an email request.
The core objective is establishing proof of message origin and authenticity.
2
Evaluate candidate security concepts
Non-repudiation provides cryptographic assurance that binds sender identity to the message payload, preventing denial of authorship.
Digital signatures supporting non-repudiation ensure both authenticity and origin validation.

Key Concept

Non-Repudiation in Security Architecture
Question 171Question

Match each deception technology term on the left with its corresponding operational description on the right.

Click a left item, then click its matching right item

Items

Honeypot
Honeyfile
Honeynet
Honeytoken

Matches

Show answer & explanation

Answer

Honeypot matches with an individual decoy system designed to attract attackers away from production assets. Honeyfile matches with an intentionally attractive dummy document placed to trigger alerts when accessed. Honeynet matches with an entire network segment of decoy systems to study network-wide attacks. Honeytoken matches with a fake piece of data like an API key or credential embedded to track unauthorized usage.
Each deception technology serves a specific operational purpose: Honeypot acts as an individual decoy host; Honeyfile acts as a decoy file; Honeynet acts as an entire decoy network infrastructure; Honeytoken acts as a tracking data element such as an API key or fake credential.

Step-by-Step Solution

1
Identify single decoy hosts vs. full decoy network structures.
Recognize that a single decoy host is a Honeypot, whereas a full subnet of decoy hosts is a Honeynet.
Scope distinguishes single system traps (honeypots) from network-level environments (honeynets).
2
Differentiate between decoy files and embedded decoy data artifacts.
Map files/documents to Honeyfiles and embedded elements like API keys or credentials to Honeytokens.
Honeyfiles represent discrete documents, while honeytokens represent data elements used as triggers.

Key Concept

Deception and Disruption Technologies
Estimated Time:1m 0s
Question 172Question

A security analyst is categorizing corporate IT procedures according to the core components of the AAA framework. Match each operational scenario to the AAA component it primarily demonstrates.

Click a left item, then click its matching right item

Items

A remote employee enters a username, password, and a time-based one-time password (TOTP) from an authenticator app to log into the corporate VPN.
The network gateway checks an employee's group membership and grants read-only access to HR records while denying edit rights.
A syslog server records time-stamped entries detailing every database table queried during an administrator's remote database session.

Matches

Show answer & explanation

Answer

Matching credential verification to Authentication, permission enforcement to Authorization, and activity logging to Accounting.
Authentication handles proof of identity (passwords, multi-factor tokens). Authorization manages permission policies and resource boundaries (read/write rights based on roles). Accounting captures historical logs, metrics, and audit records of user actions.

Step-by-Step Solution

1
Identify the purpose of credential verification (username, password, TOTP).
Confirming the user's identity corresponds to Authentication.
Authentication asks 'Who are you?' and validates claims with credentials.
2
Analyze the process of checking access rights and group policies for resource usage.
Restricting access levels based on roles corresponds to Authorization.
Authorization asks 'What are you allowed to do?' and enforces permissions.
3
Examine the function of recording timestamps and user queries into audit logs.
Tracking active usage and generating audit trails corresponds to Accounting.
Accounting asks 'What did you do?' and maintains records for tracking and auditing.

Key Concept

Core Pillars of Authentication, Authorization, and Accounting (AAA)
Question 173Question

A system administrator is configuring access control for an enterprise network. Before a user is granted permissions to access sensitive network shares, the system must first verify who the user claims to be using a username and password. Which pillar of the Authentication, Authorization, and Accounting (AAA) framework is being performed during this initial identity verification step?

Show answer & explanation

Answer: Authentication

Answer

Authentication
Authentication is the primary pillar of AAA responsible for verifying identity credentials (such as passwords, tokens, or biometrics) to confirm that a user is who they claim to be before granting access.

Step-by-Step Solution

1
Analyze the scenario task
The system is verifying the user's claimed identity via username and password credentials.
Identifying who a user claims to be is the core purpose of authentication.
2
Map the task to the AAA framework components
Identity verification maps directly to Authentication.
Authorization specifies permissions and Accounting logs activities, whereas Authentication handles initial identity verification.

Key Concept

Authentication in the AAA Framework
Question 174Question

A security architect for a regional energy utility is reviewing security mechanisms implemented across the smart grid infrastructure. Match each technical security control scenario on the left with the primary CIA Triad pillar or Non-Repudiation objective it satisfies on the right.

Click a left item, then click its matching right item

Items

Substation operators must authenticate using individual hardware tokens to generate asymmetric digital signatures on remote circuit breaker tripping commands, preventing engineers from claiming an unauthorized shutdown command originated elsewhere.
Smart meter consumption telemetry transmitted over public wireless infrastructure is encrypted with AES-256-GCM to prevent unauthorized third parties from snooping on customer power usage patterns.
Firmware images distributed to remote terminal units (RTUs) incorporate cryptographic hash trees (Merkle trees) to verify that code has not been altered or corrupted prior to installation.
Control center supervisory networks employ redundant network paths, dual power supplies, and automatic failover clustering to ensure continuous operational visibility during hardware faults.

Matches

Show answer & explanation

Answer

The operator authentication control with asymmetric digital signatures matches Non-Repudiation. Encrypting smart meter telemetry with AES-256-GCM matches Confidentiality. Firmware hash tree verification matches Integrity. Redundant paths and failover clustering match Availability.
Each technical scenario corresponds to a foundational security objective: asymmetric signing of commands provides Non-Repudiation by uniquely binding actions to individual operators; payload encryption protects customer usage privacy under Confidentiality; cryptographic hashing verifies unauthorized code modifications under Integrity; and system redundancy maintains uninterrupted operational access under Availability.

Step-by-Step Solution

1
Analyze the hardware token and asymmetric signature control for tripping commands.
Digital signatures link specific commands to an individual's private key, establishing undeniable proof of origin.
Non-repudiation prevents an entity from denying an action or transaction performed.
2
Analyze the AES-256-GCM encryption of smart meter telemetry.
Encryption shields sensitive customer consumption data from unauthorized eavesdropping across public links.
Confidentiality ensures data is accessible only to authorized entities.
3
Analyze the cryptographic hash tree verification for RTU firmware.
Hashing confirms that the firmware payload remains unaltered from its original authorized state.
Integrity guards against improper data modification or destruction.
4
Analyze the redundant network paths and automatic failover architecture.
High-availability controls prevent single points of failure from causing system downtime.
Availability ensures timely and reliable access to and use of information.

Key Concept

Core Security Goals (CIA Triad and Non-Repudiation)
Question 175Question

A cloud operations team configures an automated logging mechanism to record high-privilege configuration changes across production servers. The system computes a Hash-based Message Authentication Code (HMAC) for each log entry using a single symmetric key shared among all system administrators. Following an unauthorized system modification, an administrator denies executing the change, claiming that any user with access to the shared key could have forged the log entry. Which of the following security goals failed to be established by this logging design?

Show answer & explanation

Answer: Non-repudiation

Answer

Non-repudiation is the security goal that failed to be established because shared symmetric keys cannot uniquely trace an action to a specific individual.
Non-repudiation provides indisputable proof of the origin and integrity of data such that the sender/creator cannot deny having performed the action. When symmetric keys are shared among multiple users (such as in standard HMAC implementations), any holder of the key can generate valid message authentication codes. As a result, individual attribution is lost, preventing the establishment of non-repudiation. Digital signatures utilizing asymmetric cryptography (where each user holds a unique private key) are required to achieve non-repudiation.

Step-by-Step Solution

1
Analyze the technical control used in the scenario.
The logging system uses a Hash-based Message Authentication Code (HMAC) with a shared symmetric key.
Symmetric cryptography uses the same key for generation and verification across all authorized parties.
2
Evaluate the security guarantees of the control.
HMAC provides data integrity and proof that someone possessing the secret key created the log, but it cannot identify which specific user signed it.
Because all system administrators possess the identical symmetric key, any administrator could have produced the valid signature.
3
Map the limitation to the corresponding core security principle.
Inability to prove individual accountability means non-repudiation is lost.
To achieve non-repudiation, asymmetric cryptography (such as private key digital signatures) must be used so that only one unique individual could have authored the entry.

Key Concept

Non-Repudiation vs Integrity in Cryptographic Controls
Question 176Question

An enterprise security architect is mapping operational security controls to primary security principles within a multi-tier datacenter deployment. Match each operational control on the left with the corresponding core CIA Triad or Non-Repudiation goal on the right.

Click a left item, then click its matching right item

Items

Enforcing AES-256 full disk encryption on database storage volumes holding sensitive client records
Verifying SHA-256 cryptographic checksums of software installation packages prior to deployment
Deploying redundant uninterruptible power supply (UPS) units and automated backup generators
Requiring system administrators to digitally sign security policy updates using individual asymmetric private keys

Matches

Show answer & explanation

Answer

Full disk encryption corresponds to Confidentiality. Cryptographic checksum verification corresponds to Integrity. Redundant power systems correspond to Availability. Asymmetric digital signatures on administrative updates correspond to Non-Repudiation.
Each operational control serves a specific primary security pillar: encryption prevents unauthorized viewing (Confidentiality), checksum comparison ensures data remains unaltered (Integrity), redundant power infrastructure maintains continuous service uptime (Availability), and asymmetric key signatures cryptographically tie an operation to a specific actor so they cannot deny performing it (Non-Repudiation).

Step-by-Step Solution

1
Analyze the primary objective of each listed technical or operational control.
Encryption obscures data from unauthorized eyes; checksums detect unauthorized changes; power redundancy prevents service outage; digital signatures bind actions to a specific identity.
Understanding the security function of each control is necessary before categorizing it within foundational security frameworks.
2
Map each control objective to its foundational security pillar.
Obscuring data maps to Confidentiality; detecting alterations maps to Integrity; preventing outages maps to Availability; binding identity to an immutable action maps to Non-Repudiation.
This completes the precise alignment between implementation mechanisms and security principles.

Key Concept

CIA Triad and Non-Repudiation
Question 177Question

An energy distribution company is upgrading its remote terminal unit (RTU) fleet across regional sub-stations. The security engineering team must implement a mechanism for over-the-air (OTA) control command execution. The system must guarantee that once a lead control engineer issues a high-voltage switching instruction, the engineer cannot later deny having authorized the command, and the RTUs can verify both origin authenticity and data integrity. Which of the following technical controls best satisfies this security requirement?

Show answer & explanation

Answer: Digitally signing the command payload using the lead control engineer's private key

Answer

Digitally signing the command payload using the lead control engineer's private key
Digitally signing the payload with a private key provides non-repudiation because only the private key owner could have generated the signature. Anyone with the corresponding public key can verify integrity and authenticity, preventing the sender from denying their action.

Step-by-Step Solution

1
Analyze the core security requirement stated in the scenario.
The requirement asks for origin authenticity, integrity, and non-repudiation (ensuring the author cannot deny issuing the command).
Identifying the required security objective isolates asymmetric digital signatures from simple hashing or symmetric encryption solutions.
2
Evaluate cryptographic mechanisms against the non-repudiation property.
Only asymmetric cryptography (where only the signer holds the private key) provides non-repudiation. Symmetric mechanisms (HMAC/AES) rely on shared keys, allowing either party with the key to produce the payload.
If keys are shared, proof of specific authorship is lost, failing the non-repudiation requirement.

Key Concept

Non-Repudiation through Asymmetric Digital Signatures
Estimated Time:1m 15s
Question 178Question

During a security audit of an enterprise infrastructure, a analyst discovers that network administrators authenticate via a central RADIUS server using multi-factor authentication (MFA). However, once authenticated, any administrator gains full privileged access across all routers and switches, and individual command executions are not recorded in audit logs. The CISO mandates an updated architecture that enforces granular, role-based command execution limits and records every individual command invoked during administrator sessions. Which protocol migration and AAA pillar focus directly fulfills the CISO's mandate?

Show answer & explanation

Answer: Migrate from RADIUS to TACACS+ to separate AAA functions, leveraging TACACS+ per-command authorization for granular command restrictions and TACACS+ accounting for individual command auditing.

Answer

Migrate from RADIUS to TACACS+ to separate AAA functions, leveraging TACACS+ per-command authorization for granular command restrictions and TACACS+ accounting for individual command auditing.
TACACS+ decouples authentication, authorization, and accounting into distinct processes. In administrative device management scenarios, TACACS+ allows every single command entered by an administrator to be sent to the AAA server for authorization before execution, while recording precise per-command accounting logs to satisfy compliance and audit mandates.

Step-by-Step Solution

1
Analyze the existing deficiency in the AAA architecture
The current RADIUS deployment provides Authentication (verifying identity via MFA) but lacks granular Authorization (restricting specific commands per role) and detailed Accounting (logging individual commands).
RADIUS binds authentication and authorization together and does not support command-by-command evaluation.
2
Evaluate protocol features for administrative device management
TACACS+ separates all three AAA components and operates over TCP (port 49), allowing individual command authorization requests and detailed per-command accounting logs.
TACACS+ is specifically designed for enterprise administrator management of network device shells.
3
Select the control solution that directly fulfills both requirements of the mandate
Transitioning to TACACS+ enables per-command authorization (role-based limits) and per-command accounting (audit recording).
This directly completes the missing Authorization and Accounting pillars required by the scenario.

Key Concept

Authentication, Authorization, and Accounting (AAA) Protocol Differences (RADIUS vs TACACS+)
Estimated Time:2m 0s
Question 179Question

A cloud compliance team is configuring an automated log aggregation vault to collect audit trails from independent third-party SaaS vendors. The organization mandates two primary security requirements for all ingested logs: first, the vault must be able to prove that a log file was not modified after creation; second, the log file must provide non-repudiation, ensuring that an untrusted vault administrator who possesses read access cannot forge a valid log entry on behalf of any vendor. Which of the following cryptographic techniques should each vendor apply to the log files prior to transmission to meet all audit requirements?

Show answer & explanation

Answer: Sign the log file using the vendor's private key to generate an asymmetric digital signature appended to the payload.

Answer

The correct technique is signing the log file using the vendor's private key to generate an asymmetric digital signature.
Generating an asymmetric digital signature by hashing the log file and encrypting the hash digest with the vendor's private key guarantees both integrity and non-repudiation. Anyone can verify the signature using the vendor's public key, but no one—including the untrusted vault administrator—can forge a valid signature without access to the vendor's private key.

Step-by-Step Solution

1
Analyze the security requirements specified in the scenario
Identified the need for both data integrity (detecting post-creation modifications) and non-repudiation (preventing an untrusted vault administrator with key access from forging log entries).
Non-repudiation requires asymmetric cryptography where only the producing entity possesses the signing key.
2
Evaluate symmetric vs. asymmetric cryptographic primitives for proof of origin
Symmetric primitives (like HMAC with shared keys) allow any key holder to generate valid tags, failing non-repudiation. Asymmetric digital signatures (private key signing, public key verification) ensure only the private key owner can produce valid signatures.
The vault administrator cannot forge signatures without the vendor's private key.
3
Select the option fulfilling both integrity and non-repudiation
Digitally signing the log payload using the vendor's private key fulfills all stated audit and security criteria.
Verification using the vendor's public key confirms both that the file was unchanged and that it originated from that specific vendor.

Key Concept

Digital Signatures and Non-Repudiation
Question 180Question

An IT security administrator is implementing the Authentication, Authorization, and Accounting (AAA) framework for remote access connections. Which of the following tasks directly represent the Accounting component of AAA? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Logging user session duration and total network data volume transferred; Recording login timestamps and authentication attempt outcomes in an audit repository

Answer

Logging user session duration and total network data volume transferred, and recording login timestamps and authentication attempt outcomes in an audit repository.
Accounting focuses on tracking user activity, auditing actions, and measuring resource consumption such as connection duration, transferred bytes, and login history logs.

Step-by-Step Solution

1
Define the primary responsibility of each AAA pillar
Authentication verifies identity, Authorization determines permissions, and Accounting logs actions, session metrics, and audit histories.
Understanding the distinct boundaries of AAA components allows proper classification of administrative tasks.
2
Evaluate each task option against the Accounting definition
Logging resource usage (session length, byte counts) and keeping audit logs (login timestamps) fall under Accounting. Credential verification falls under Authentication, while permission enforcement falls under Authorization.
Accounting is explicitly responsible for telemetry, data tracking, and historical audit trails.

Key Concept

Authentication, Authorization, and Accounting (AAA) - Accounting Functions
PreviousPage 9 / 14Next
General Security Concepts Practice Questions — CompTIA Security+ — Page 9 | Examkin