Security Architecture

405 soru

Soru 361Soru

An enterprise administrator configures a server with a RAID 5 disk array to ensure continuous availability in the event of a storage drive failure. Following a ransomware incident that encrypted all files on the volume, the administrator replaces one of the physical hard drives with a new spare disk, expecting the rebuild process to recover the original unencrypted files. Which of the following best explains why this recovery strategy failed?

Cevabı ve açıklamayı göster

Cevap: RAID provides fault tolerance against hardware failure, but write operations—including file encryption—are immediately calculated across the array, preserving corrupt states.

Cevap

RAID provides fault tolerance against hardware failure, but write operations—including file encryption—are immediately calculated across the array, preserving corrupt states.
Redundancy mechanisms like RAID 5 are designed to provide fault tolerance against physical hardware failure by spreading data and parity across multiple disks. However, RAID operates at the storage level and processes all write operations immediately. When ransomware encrypts files, those changes are parity-encoded across the array. Rebuilding a drive merely recalculates the existing array state, which includes the encrypted data, demonstrating that fault tolerance is not a replacement for independent point-in-time backups.

Adım Adım Çözüm

1
Analyze the technology implemented in the scenario.
The server uses RAID 5 for storage fault tolerance.
RAID 5 uses block-level striping with distributed parity to sustain a single physical disk failure without losing access to volume data.
2
Evaluate the nature of the data loss incident.
Ransomware maliciously modified (encrypted) the logical file contents.
Encryption is a logical file system operation, not a physical hardware failure.
3
Differentiate between redundancy/fault tolerance and backup/recovery controls.
Replacing a disk rebuilds missing parity/data blocks based on current (encrypted) disk contents.
Redundancy ensures system availability during hardware failures but immediately processes and replicates logical data changes, requiring separate offline backups for point-in-time recovery.

Anahtar Kavram

Distinction between Fault Tolerance/Redundancy (RAID) and Data Backups
Soru 362Soru

A medical device company is designing a connected infusion pump deployed in hospital environments. To protect against malicious firmware modifications and unauthorized code execution during startup, the device must verify the signature of the boot loader using a cryptographic key burned into immutable hardware during manufacturing. Which hardware-based security control establishes this initial unalterable anchor for cryptographic boot chain verification?

Cevabı ve açıklamayı göster

Cevap: Hardware Root of Trust

Cevap

Hardware Root of Trust provides the unalterable hardware anchor required to verify digital signatures during the boot process.
The Hardware Root of Trust is an inherently trusted hardware component (such as immutable ROM or write-once eFuses) that holds the cryptographic key or hash used to initiate the secure boot process. Because it cannot be altered by software or firmware updates, it serves as the ultimate anchor of trust for verifying subsequent stages of execution.

Adım Adım Çözüm

1
Analyze the scenario requirements
The requirement calls for a hardware-anchored, immutable cryptographic validation mechanism to prevent unauthorized firmware execution during device boot.
Embedded security relies on hardware primitives to establish trust before software executes.
2
Evaluate hardware security mechanisms
A Hardware Root of Trust uses read-only memory (ROM) or electronic fuses (eFuses) configured at manufacturing to store public keys or hash measurements safely.
Because this memory cannot be modified by software, it forms the trusted baseline for secure boot validation.
3
Select the matching control
Hardware Root of Trust correctly fulfills the requirement.
It ensures that boot integrity validation originates from an unalterable hardware component.

Anahtar Kavram

Hardware Root of Trust and Secure Boot Validation
Soru 363Soru

A system architect is designing high-availability storage connectivity for a mission-critical database server connected to a Storage Area Network (SAN). The design must ensure continuous data access even if a host bus adapter (HBA), interconnect cable, or SAN switch fails, while also balancing traffic across active pathways. Which of the following architectural controls should the security architect implement to fulfill this requirement?

Cevabı ve açıklamayı göster

Cevap: Multipath I/O (MPIO)

Cevap

Multipath I/O (MPIO) is the correct architectural control to provide high availability and load balancing for SAN storage connectivity across redundant host bus adapters and storage switches.
Multipath I/O (MPIO) is designed specifically to leverage multiple physical connections (host bus adapters, cables, and SAN switches) between a server and a storage array. It provides automatic path failover and load balancing, ensuring continuous operational availability if any single network path component fails.

Adım Adım Çözüm

1
Analyze the technical requirements of the scenario.
The requirement calls for fault tolerance and load balancing across storage interface hardware (HBAs), cabling, and SAN switches for block-level storage access.
Identifying the layer of redundancy needed (storage network transport vs. internal disk array vs. Ethernet LAN) directs the selection of the correct control.
2
Evaluate the capabilities of storage-specific redundant pathway controls.
Multipath I/O (MPIO) recognizes duplicate paths to the same block storage target, dynamically routing traffic around failed host adapters, SAN switches, or cables without dropping the connection.
MPIO operates specifically at the operating system storage driver layer to aggregate separate physical SAN pathways.
3
Differentiate MPIO from non-applicable redundancy controls.
RAID protects local disks, backups provide point-in-time recovery, and standard LACP handles local Ethernet switch ports rather than SAN block storage fabrics.
Preventing single points of failure in storage networks requires path redundancy designed specifically for Fibre Channel or iSCSI storage controllers.

Anahtar Kavram

Multipath I/O (MPIO) for SAN Redundancy
Tahmini Süre:1m 30s
Soru 364Soru

A security engineer is designing an embedded industrial sensor node deployed in untrusted physical locations. The design requires that the system only executes cryptographically signed boot code during power-on to prevent unauthorized firmware modifications. Which of the following hardware security controls should the engineer implement to fulfill this requirement?

Cevabı ve açıklamayı göster

Cevap: Hardware Root of Trust with Secure Boot

Cevap

Hardware Root of Trust with Secure Boot
The combination of a Hardware Root of Trust and Secure Boot anchors security in immutable read-only memory (such as internal boot ROM or eFuses). During device bootup, the hardware Root of Trust cryptographically verifies the digital signature of the bootloader before executing it, ensuring that altered or untrusted firmware cannot run.

Adım Adım Çözüm

1
Analyze the hardware security requirement
The scenario requires ensuring that only cryptographically signed boot code runs at startup to prevent unauthorized firmware modification on an embedded device.
Embedded hardware in untrusted physical environments requires cryptographic validation of firmware before execution.
2
Evaluate hardware-based security controls
Secure Boot anchored in a hardware Root of Trust uses immutable boot ROM keys to verify the signature of the bootloader image.
This establishes a cryptographically validated chain of trust from initial hardware power-on through operating system execution.
3
Differentiate from software, cryptographic payload, or detective controls
Software agents, data-at-rest encryption, and logging operate post-boot or focus on confidentiality rather than early boot signature validation.
Hardware boot verification must occur prior to any software-level control execution.

Anahtar Kavram

Hardware Root of Trust and Secure Boot
Tahmini Süre:1m 15s
Soru 365Soru

A financial technology organization is refactoring its internal microservices communication architecture to align with Zero Trust Architecture (ZTA) principles. An application security architect specifies that internal services must no longer trust incoming network traffic based on IP subnets or internal network placement. Instead, every request must be dynamically evaluated against contextual security policies and session health attributes before access is granted. Which logical component within the Zero Trust framework is directly responsible for evaluating these access policies and rendering the authorization decision?

Cevabı ve açıklamayı göster

Cevap: Policy Decision Point (PDP)

Cevap

The Policy Decision Point (PDP) is the component responsible for evaluating access policies and rendering authorization decisions.
The Policy Decision Point (PDP) is the ultimate decision-making component in a Zero Trust Architecture. It receives contextual telemetry (such as user identity, device posture, and risk factors), compares it against enterprise security policies, and outputs an authorization determination.

Adım Adım Çözüm

1
Identify the primary responsibility described in the scenario
The requirement is to evaluate dynamic contextual policies and render an authorization decision for microservices requests.
Zero Trust Architecture separates the decision-making control plane from the enforcement data plane.
2
Differentiate between Zero Trust control plane functional components
The Policy Decision Point (PDP) makes authorization decisions, whereas the Policy Enforcement Point (PEP) enforces those decisions at the traffic gate.
Understanding the division of responsibilities ensures correct architecture design.

Anahtar Kavram

Zero Trust Policy Decision Point (PDP) vs Policy Enforcement Point (PEP)
Soru 366Soru

A financial enterprise is deploying specialized infrastructure across regional offices to process centralized database transaction encryption. The security team requires a dedicated hardware-based solution capable of performing high-throughput cryptographic operations while securely storing master keys. The device must ensure keys cannot be extracted even if an adversary gains root access to the host operating system or opens the chassis physical casing. Which of the following hardware security controls best meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Hardware Security Module (HSM)

Cevap

A Hardware Security Module (HSM) is the appropriate control because it provides physical tamper-responsive protection and isolated cryptographic processing for master keys independent of host operating system security.
A Hardware Security Module (HSM) is a hardened, plug-in or external device dedicated to safeguarding digital keys and accelerating cryptographic operations. HSMs feature specialized physical security measures (such as tamper-detecting covers and zeroization circuits) that protect stored keys against both physical access and host system compromise.

Adım Adım Çözüm

1
Identify the core requirements from the scenario
Requirements demand a hardware device that isolates cryptographic keys, processes high-throughput transactions, resists physical chassis intrusion, and remains secure even if host OS root access is compromised.
Analyzing security constraints guides selecting between platform microcontrollers, storage controls, and specialized cryptographic appliances.
2
Evaluate hardware security mechanisms against requirements
An HSM is specifically engineered as a tamper-resistant hardware security enclave designed for dedicated master key lifecycle management and isolated cryptographic processing.
Host-bound microcontrollers (like TPMs) and local disk encryption (like SEDs) do not fulfill high-throughput centralized key appliance demands with active physical zeroization.

Anahtar Kavram

Hardware Security Module (HSM) functionality and tamper protection
Soru 367Soru

Match each enterprise identity and access management (IAM) protocol to its corresponding architectural use case and operational characteristic.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

OAuth 2.0
OpenID Connect (OIDC)
RADIUS
TACACS+

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

OAuth 2.0 matches delegated API authorization; OpenID Connect matches user authentication extensions on OAuth 2.0; RADIUS matches UDP-based combined network AAA; TACACS+ matches fully encrypted TCP-based administrator device access.
Each protocol is paired according to its native architectural function: OAuth 2.0 provides delegated authorization, OIDC adds user authentication via ID tokens, RADIUS provides combined UDP-based network AAA, and TACACS+ provides fully encrypted, decoupled TCP device management AAA.

Adım Adım Çözüm

1
Differentiate between authorization frameworks and identity layers for web applications.
Identify OAuth 2.0 as the core delegated authorization framework and OIDC as the identity authentication layer.
OAuth 2.0 issues access tokens for APIs, while OIDC adds ID tokens for user identity.
2
Analyze network access protocols vs device administration AAA protocols.
Identify RADIUS for UDP network access AAA and TACACS+ for TCP administrator AAA.
RADIUS combines auth/authz over UDP, whereas TACACS+ separates auth/authz and encrypts full payloads over TCP.

Anahtar Kavram

Identity and Access Management Architecture Protocols
Soru 368Soru

An enterprise logistics organization is re-architecting its cloud-native platform to comply with NIST SP 800-207 Zero Trust Architecture (ZTA) principles. Which of the following architectural practices must be implemented to establish core Zero Trust controls across the environment? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Enforce explicit authentication and authorization for every access request, utilizing dynamic context such as identity, device state, and location regardless of network position.; Implement microsegmentation and end-to-end session encryption between workload components to minimize the blast radius of potential compromises.

Cevap

The core architectural practices required are explicitly verifying every access request using dynamic risk context, and implementing microsegmentation with end-to-end encryption between workload components to contain lateral movement.
Zero Trust Architecture requires explicit verification of every access request using dynamic contextual signals (identity, device posture, location) regardless of network origin, combined with granular microsegmentation and encryption between internal services to assume breach and limit lateral movement.

Adım Adım Çözüm

1
Identify fundamental Zero Trust Architecture (ZTA) tenets
ZTA relies on assuming breach, explicitly verifying all connections, enforcing least privilege, and continuously monitoring access context.
Implicit network trust based on physical location or static perimeters must be removed.
2
Map tenets to enterprise workload controls
Verifying each request dynamically (explicit verification) and segmenting internal workload flows (microsegmentation) directly enact these tenets.
These controls restrict access to authorized subjects and limit lateral movement if a workload is compromised.

Anahtar Kavram

Zero Trust Architecture Principles
Tahmini Süre:1m 30s
Soru 369Soru

An enterprise security team is implementing a Zero Trust Identity and Access Management (IAM) architecture. The team needs to ensure that access to cloud resources is dynamically granted or restricted based on real-time signals, such as user risk level, device health state, and geographic location, rather than relying solely on static group memberships or initial password verification. Which of the following IAM architectural mechanisms should the team implement to satisfy this requirement?

Cevabı ve açıklamayı göster

Cevap: Context-aware access policies

Cevap

Context-aware access policies
Context-aware access policies evaluate real-time signals—such as user IP location, device security posture, and behavioral risk scores—to dynamically enforce granular access controls in alignment with Zero Trust architecture principles.

Adım Adım Çözüm

1
Analyze the architecture requirements in the scenario.
Identified the need for real-time, dynamic access decisions using contextual signals like device health, location, and risk scores.
Zero Trust IAM architecture mandates continuous evaluation rather than one-time static authentication.
2
Evaluate candidate IAM access control mechanisms against dynamic requirements.
Context-aware access policies evaluate incoming telemetry continuously against policy parameters.
Static models like RBAC or MAC cannot dynamically adapt access rights based on real-time situational signals.

Anahtar Kavram

Context-Aware Conditional Access in IAM Architecture
Soru 370Soru

An enterprise security architect is transitioning legacy perimeter security controls to align with Zero Trust Architecture (ZTA) design tenets. Match each Zero Trust architectural concept on the left to its corresponding operational function on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Implicit Trust Zone Removal
Continuous Adaptive Risk Evaluation
Microsegmentation
Control Plane and Data Plane Separation

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Implicit Trust Zone Removal corresponds to eliminating default trust based on network location. Continuous Adaptive Risk Evaluation corresponds to dynamically re-evaluating session state and context throughout an active connection. Microsegmentation corresponds to dividing network environments into small isolated zones to restrict lateral movement. Control Plane and Data Plane Separation corresponds to decoupling policy decision logic from application traffic paths.
Each Zero Trust term matches its core architectural operational responsibility: removing implicit trust strips location-based assumptions; continuous adaptive evaluation continuously monitors session context; microsegmentation restricts internal lateral movement; and control/data plane separation decouples policy management from data transit paths.

Adım Adım Çözüm

1
Analyze the core premise of Zero Trust regarding network location and implicit trust.
Identify that removing implicit trust eliminates reliance on physical or IP-based network location.
Legacy networks trust internal IP segments; Zero Trust demands zero inherent trust regardless of location.
2
Evaluate session lifetime management principles in Zero Trust.
Map Continuous Adaptive Risk Evaluation to ongoing context and behavioral re-validation.
Authentication and authorization must not be static single-point-in-time checks.
3
Analyze containment strategies within Zero Trust Architecture.
Map Microsegmentation to creating granular isolated zones around workloads to prevent lateral movement.
Breach containment relies on restricting traffic between workload segments.
4
Examine architectural component separation.
Map Control Plane and Data Plane Separation to isolating policy evaluation logic from data traffic transmission.
Policy engines and administrators process control requests independently of raw data forwarding paths.

Anahtar Kavram

Zero Trust Architecture Principles
Soru 371Soru

A renewable energy utility operates remote maintenance workstations connected to solar farm Supervisory Control and Data Acquisition (SCADA) controllers. Under the existing access model, once a field technician completes initial multi-factor authentication (MFA) at the start of their shift, the active network connection is granted persistent trust across all internal SCADA subnets. The organization wants to refactor this workflow to align with core Zero Trust Architecture principles. Which of the following implementation strategies best satisfies this requirement?

Cevabı ve açıklamayı göster

Cevap: Continuously evaluating user risk metrics and endpoint compliance signals before granting access to each subsequent SCADA resource.

Cevap

Continuously evaluating user risk metrics and endpoint compliance signals before granting access to each subsequent SCADA resource represents the correct implementation of Zero Trust principles.
Zero Trust Architecture eliminates implicit trust tied to network location or past authentication. By continuously evaluating contextual risk factors—such as user activity, endpoint security posture, and resource sensitivity—before granting access to specific assets, the system maintains strict explicit verification at all times.

Adım Adım Çözüm

1
Analyze the existing architecture weakness described in the scenario.
The current model relies on persistent, implicit trust across network subnets after an initial shift authentication.
Zero Trust Architecture explicitly forbids granting implicit trust based solely on initial authentication or network location.
2
Evaluate the architectural controls against Zero Trust core tenets.
Dynamic assessment of device posture, context, and user risk scores for every individual resource request removes implicit trust and enforces explicit verification continuously.
Zero Trust requires continuous authorization evaluations rather than one-time perimeter access.

Anahtar Kavram

Continuous explicit verification and elimination of implicit trust in Zero Trust Architecture
Soru 372Soru

A security administrator is evaluating a high-availability perimeter firewall pair deployed in an active-passive failover configuration. During a scheduled failover simulation, the secondary appliance successfully assumed the virtual IP address and began handling traffic, but all active client TCP sessions were abruptly dropped, forcing users to re-authenticate. The administrator must update the architecture so that existing connection states persist uninterrupted across failover events. Which of the following solutions should the administrator implement?

Cevabı ve açıklamayı göster

Cevap: Stateful session synchronization across the cluster members

Cevap

Stateful session synchronization across the cluster members
Stateful session synchronization continuously transmits connection tracking data, NAT tables, and TCP state details across a dedicated heartbeat/sync interface between high-availability nodes. When the passive node assumes primary status, it already possesses the exact state of all active connections, enabling uninterrupted traffic flow without forcing clients to re-establish connections.

Adım Adım Çözüm

1
Analyze the observed issue during the active-passive firewall failover test.
The secondary node successfully acquired network ownership (virtual IP), but dropped active client TCP connections, indicating a lack of dynamic session state sharing.
Basic high availability virtual IP mechanisms (like VRRP or CARP) manage IP address migration but do not natively copy active memory tables across hosts.
2
Evaluate the architectural control required for seamless session persistence.
Stateful session synchronization must be configured over a dedicated sync link to continuously replicate session state tables.
This allows the backup appliance to track open TCP connections and immediately service existing client traffic without requiring session re-establishment.

Anahtar Kavram

Stateful Session Failover vs. Hardware Fault Tolerance
Tahmini Süre:1m 15s
Soru 373Soru

A security architect is evaluating hardware security controls for enterprise hardware and embedded system deployments. Match each hardware security component on the left to its corresponding security capability on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Secure Element (SE)
Baseboard Management Controller (BMC)
Memory Protection Unit (MPU)
Hardware Root of Trust (eFuse / Immutable ROM)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct matches pair Secure Element (SE) with tamper-resistant credential storage; Baseboard Management Controller (BMC) with out-of-band remote management; Memory Protection Unit (MPU) with hardware memory region isolation; and Hardware Root of Trust (eFuse / Immutable ROM) with unalterable boot validation.
Each hardware component is correctly mapped to its essential function: Secure Elements handle isolated credential and key storage; Baseboard Management Controllers perform out-of-band remote administration; Memory Protection Units enforce internal memory access restrictions; and Hardware Roots of Trust anchor secure boot validation using immutable hardware.

Adım Adım Çözüm

1
Evaluate the functional scope of a Secure Element (SE).
Identified as a specialized, tamper-resistant chip designed to store sensitive tokens and biometric data securely.
SE provides physical and logical isolation from the main operating system for crypto operations.
2
Evaluate the architectural role of a Baseboard Management Controller (BMC).
Identified as out-of-band motherboard hardware that enables remote administration.
BMCs function independently of the main processor and host operating system.
3
Evaluate the mechanism of a Memory Protection Unit (MPU).
Identified as micro-architectural hardware that restricts execution regions and memory access.
MPUs enforce boundary protection in embedded hardware to block buffer overflows and privilege escalation.
4
Evaluate the purpose of a Hardware Root of Trust built on eFuse or Immutable ROM.
Identified as the static cryptographic foundation for boot validation.
Write-once or read-only hardware cannot be overwritten by software malware, forming an immutable trust anchor.

Anahtar Kavram

Hardware Security Components and Embedded Controls
Soru 374Soru

A municipal water utility is re-architecting remote operational telemetry monitoring access for field maintenance engineers. The security architect must enforce Zero Trust Architecture (ZTA) principles to prevent unauthorized lateral movement across operational technology (OT) networks. Which of the following access control implementations best demonstrates the core Zero Trust tenets of explicit verification and least privilege?

Cevabı ve açıklamayı göster

Cevap: Deploying an inline Policy Enforcement Point (PEP) that evaluates user identity, endpoint health, and contextual risk for every individual database query before granting per-session access.

Cevap

Deploying an inline Policy Enforcement Point (PEP) that evaluates user identity, endpoint health, and contextual risk for every individual database query before granting per-session access.
The option specifying an inline Policy Enforcement Point (PEP) directly aligns with NIST SP 800-207 Zero Trust Architecture principles. It enforces explicit verification by continuously inspecting user identity, device compliance posture, and contextual parameters for every database transaction, granting minimal per-session access without assuming network-based implicit trust.

Adım Adım Çözüm

1
Analyze the core requirements of Zero Trust Architecture (ZTA).
ZTA requires eliminating implicit trust based on network location and enforcing continuous explicit verification and least privilege for every access request.
Traditional perimeter security assumes internal network traffic is trustworthy, whereas Zero Trust assumes breach and verifies continuously.
2
Evaluate the role of Policy Decision Points (PDP) and Policy Enforcement Points (PEP).
An inline PEP intercepting every transaction ensures dynamic contextual evaluation (user identity, device posture, location, risk) before granting temporal, per-session authorization.
Explicit verification must occur dynamically on a per-request basis rather than relying on a one-time perimeter check.

Anahtar Kavram

Zero Trust Architecture Principles - Explicit Verification and Continuous Authorization
Tahmini Süre:1m 30s
Soru 375Soru

Match each resilience and redundancy mechanism on the left with the corresponding operational requirement or architecture scenario on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Automatic Transfer Switch (ATS)
Geographic Asynchronous Replication
Multipath I/O (MPIO)
Dynamic BGP Multihoming

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct pairings match Automatic Transfer Switch (ATS) to single-corded utility power delivery via seamlessly transferred electrical loads; Geographic Asynchronous Replication to maintaining distant data availability with a non-zero RPO; Multipath I/O (MPIO) to storage access path aggregation over redundant HBAs; and Dynamic BGP Multihoming to enterprise boundary traffic rerouting across multiple ISP links.
Each redundancy technology directly targets a specific physical or logical component failure domain: ATS addresses single-corded power feed failure, MPIO addresses storage channel and HBA adapter failure, BGP multihoming addresses WAN ISP link failure, and Asynchronous Replication addresses regional datacenter failure without application performance degradation.

Adım Adım Çözüm

1
Analyze power redundancy requirements for single-corded hardware.
An Automatic Transfer Switch (ATS) is required to feed single-corded appliances from redundant PDUs without power interruption.
ATS handles power source failover at the rack level when a PDU or utility feed loses power.
2
Evaluate long-distance database disaster recovery methods.
Geographic Asynchronous Replication allows cross-datacenter sync over WAN without local commit latency constraints.
Asynchronous replication tolerates network latency across geographic sites while accepting a minor RPO delta.
3
Assess host-to-SAN storage link redundancy.
Multipath I/O (MPIO) aggregates multiple Host Bus Adapter (HBA) paths into a redundant logical channel.
MPIO protects host storage connectivity against individual HBA, cable, or fiber channel switch failures.
4
Examine WAN perimeter network resilience.
Dynamic BGP Multihoming maintains network connectivity across independent Internet service provider links.
BGP detects link failure and updates routing tables to direct inbound and outbound traffic over functional paths.

Anahtar Kavram

High Availability and Infrastructure Redundancy Controls
Soru 376Soru

A logistics enterprise is deploying thousands of handheld mobile terminals to remote distribution staff. The devices operate in physically untrusted environments and store sensitive customer authentication data. The security engineering team mandates that each device must validate system integrity from power-on through operating system initialization using hardware-bound cryptographic measurements, while securely storing full-disk encryption keys on a dedicated cryptoprocessor integrated into the endpoint's motherboard. Which of the following hardware security controls BEST meets this requirement?

Cevabı ve açıklamayı göster

Cevap: Trusted Platform Module (TPM)

Cevap

Trusted Platform Module (TPM)
The correct option is the Trusted Platform Module (TPM). A TPM is a hardware-based cryptoprocessor integrated into endpoint motherboards that securely generates and stores cryptographic keys, while providing platform integrity measurements (measured boot) to ensure firmware and system boot files have not been compromised.

Adım Adım Çözüm

1
Analyze the endpoint hardware security requirements specified in the scenario.
Identified two primary requirements: motherboard-integrated hardware cryptoprocessor key storage and hardware-bound platform boot integrity measurement on individual mobile endpoints.
Security controls must match both the form factor (endpoint motherboard) and functional requirements (boot integrity and key protection).
2
Evaluate hardware security mechanisms against the requirement profile.
A Trusted Platform Module (TPM) is designed specifically for endpoint systems to store cryptographic keys isolated from the main CPU and verify boot integrity metrics via Platform Configuration Registers (PCRs).
Other options either target data center infrastructure (HSM), focus strictly on storage media encryption (SED), or lack hardware-level isolation (software key stores).

Anahtar Kavram

Trusted Platform Module (TPM) and Endpoint Hardware Security
Tahmini Süre:1m 30s
Soru 377Soru

A security administrator is troubleshooting a critical network storage appliance in a data center. The appliance features dual internal power supply units (PSUs) to ensure hardware fault tolerance. However, during a recent scheduled power maintenance event on a single electrical circuit, the appliance unexpectedly lost power and shut down. Investigation reveals that both PSUs were plugged into the same rack Power Distribution Unit (PDU). Which of the following infrastructure modifications should the administrator implement to prevent single-circuit power outages from taking the appliance offline?

Cevabı ve açıklamayı göster

Cevap: Connect each power supply unit to separate, independent Power Distribution Units (PDUs) fed by distinct power sources.

Cevap

Connect each power supply unit to separate, independent Power Distribution Units (PDUs) fed by distinct power sources.
Connecting each redundant power supply unit to a separate, independent Power Distribution Unit fed by distinct power lines eliminates single points of failure in the electrical distribution path. If one PDU or utility feed goes offline, the second PSU continues to draw power from the remaining active PDU, allowing the appliance to operate without interruption.

Adım Adım Çözüm

1
Analyze the root cause of the system outage described in the scenario.
The system shut down because both redundant power supplies were plugged into the same PDU, making that PDU and its single circuit a single point of failure.
Redundant hardware components inside a chassis cannot provide high availability if they rely on a single shared upstream power source.
2
Identify the appropriate architectural modification for power redundancy.
Each power supply unit must be connected to independent PDUs backed by separate electrical circuits or Uninterruptible Power Supply (UPS) feeds.
A dual-bus power configuration ensures continuous server operation even if an entire PDU or electrical breaker trips.

Anahtar Kavram

Power Redundancy and Single Points of Failure
Tahmini Süre:1m 15s
Soru 378Soru

Match each Identity and Access Management (IAM) architectural component to its primary role within an access evaluation control framework.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Policy Decision Point (PDP)
Policy Enforcement Point (PEP)
Policy Information Point (PIP)
Policy Administration Point (PAP)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Policy Decision Point (PDP) matches authorization evaluation; Policy Enforcement Point (PEP) matches traffic interception and enforcement; Policy Information Point (PIP) matches contextual attribute retrieval; Policy Administration Point (PAP) matches policy creation and management.
In modern access control and Zero Trust architectures, access evaluation is divided across specialized functional entities. The Policy Decision Point (PDP) evaluates request parameters against access policies. The Policy Enforcement Point (PEP) enforces the resulting decision at network or application boundary gates. The Policy Information Point (PIP) supplies requisite contextual attributes (such as user attributes or threat telemetry) to the PDP. The Policy Administration Point (PAP) acts as the governance interface for policy creation and maintenance.

Adım Adım Çözüm

1
Identify the component that computes authorization logic.
Policy Decision Point (PDP) is paired with evaluating access requests to issue decisions.
The PDP evaluates rules against subject and resource attributes to generate a permit or deny outcome.
2
Identify the gateway component sitting inline with traffic.
Policy Enforcement Point (PEP) is paired with intercepting requests and enforcing decisions.
The PEP acts as a gatekeeper that blocks or permits user access based on the PDP's determination.
3
Identify the entity responsible for supplying external context.
Policy Information Point (PIP) is paired with retrieving contextual attributes.
The PIP feeds environmental variables, user group memberships, and device compliance context into the evaluation engine.
4
Identify the administration interface for policy lifecycle management.
Policy Administration Point (PAP) is paired with creating and storing policy rules.
The PAP is the administrative system where security policies are authored and published.

Anahtar Kavram

IAM Architecture Control Points (PDP, PEP, PIP, PAP)
Soru 379Soru

An electrical utility provider is deploying smart grid field concentrator units to unmonitored outdoor locations. The units will transmit sensitive metering telemetry and must be protected against physical tampering, unauthorized firmware manipulation, and key extraction. Which of the following hardware security controls should the security architect require for these embedded devices? (Select TWO).

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Implementation of a hardware Root of Trust combined with a Trusted Platform Module (TPM) to perform measured boot and secure cryptographic keys.; Integration of physical tamper detection sensors connected to active zeroization circuits to purge sensitive key material if the chassis is compromised.

Cevap

The device security architecture must incorporate a hardware Root of Trust with a TPM for measured boot integrity, along with physical tamper detection sensors linked to zeroization circuits to clear cryptographic key material upon physical intrusion.
Establishing a hardware Root of Trust with a TPM guarantees firmware integrity through measured boot and protects cryptographic keys within dedicated secure hardware. Combining this with physical tamper detection and zeroization ensures that physical intrusion results in the immediate destruction of sensitive key material, effectively mitigating both software manipulation and physical extraction risks.

Adım Adım Çözüm

1
Analyze deployment environment and threat vectors.
Identified risks including physical access, unauthorized firmware modification, and physical cryptographic key extraction on unmonitored field hardware.
Unmanned outdoor embedded infrastructure requires hardware-anchored security controls.
2
Evaluate controls for boot integrity and key isolation.
Hardware Root of Trust and TPM validate bootloader components sequentially and isolate cryptographic processes from software-layer exploits.
A TPM and hardware Root of Trust form the foundational trust anchor for verifying system integrity before executing system code.
3
Evaluate controls for physical enclosure breach.
Physical tamper detection switches linked to zeroization logic instantly wipe cryptographic keys if the outer casing is breached.
Zeroization ensures keys cannot be recovered via hardware bus probing or physical extraction once physical boundary defenses fail.

Anahtar Kavram

Hardware Root of Trust, TPM measured boot, and physical tamper zeroization mechanisms in embedded hardware security.
Soru 380Soru

An enterprise is implementing a federated web single sign-on (SSO) solution allowing corporate users to access external cloud applications seamlessly. The architectural requirement mandates using an open standard that relies on XML-based security assertions to transmit authentication state and user attributes from the Identity Provider (IdP) to the Service Provider (SP). Which of the following protocols should the security architect select to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: SAML (Security Assertion Markup Language)

Cevap

SAML (Security Assertion Markup Language) is the correct architectural choice for XML-based federated web SSO between an Identity Provider and a Service Provider.
Security Assertion Markup Language (SAML) is an open XML-based standard created specifically for federated Single Sign-On (SSO). It allows an Identity Provider (IdP) to package authentication state, user attributes, and entitlement assertions into XML tokens sent to a Service Provider (SP), perfectly satisfying all stated requirements.

Adım Adım Çözüm

1
Identify key architectural requirements from the scenario.
The requirements demand a web-based federated SSO architecture using XML-based security assertions between an Identity Provider (IdP) and a Service Provider (SP).
Accurately pinpointing protocol capability criteria is required before selecting IAM security controls.
2
Evaluate standard identity protocols against the XML assertion constraint.
Security Assertion Markup Language (SAML) specifically utilizes XML formatted security assertions to communicate user identity and authentication status across domain boundaries.
OAuth 2.0 and OIDC use JSON tokens, RADIUS uses UDP attribute-value pairs, and Kerberos uses ticket grants within symmetric domain trusts.

Anahtar Kavram

Federated Identity and Access Architecture
ÖncekiSayfa 19 / 21Sonraki