Soru

Zorluk: ZorPublic Key Infrastructure and Certificate Management

A security engineer is auditing an automated provisioning pipeline for a fleet of internal microservice gateways. The deployment script generates a single public/private key pair and Certificate Signing Request (CSR) on a central management server, submits the CSR to the internal Certificate Authority (CA), and then copies the issued certificate and private key over SSH to all target gateway nodes. Which of the following best describes the primary security flaw in this PKI workflow?

  1. The private key was generated on a central server rather than locally on each target system, increasing the attack surface and violating non-repudiation and key isolation principles.Cevap
  2. B
    The Certificate Authority (CA) should generate both the public and private key pair upon receiving administrative attributes, rather than requiring key generation on local endpoint software.
  3. C
    The central management server should use asymmetric encryption to encrypt bulk traffic across gateway nodes directly instead of requesting X.509 digital certificates.
  4. D
    Generating key pairs prior to CA validation prevents data integrity verification because digital signatures rely on shared symmetric keys matching across all destination gateways.

Cevap

The primary flaw is generating the private key on a central server and distributing it to multiple target nodes, which compromises key isolation and exposes private keys over the network.
In proper PKI design, private keys should be generated locally on the target endpoint (or within an associated HSM/TPM) and must never traverse the network. Sharing a single private key across multiple microservice gateways increases the blast radius of a credential compromise and undermines host identification and non-repudiation.

Adım Adım Çözüm

1
Analyze the PKI key generation and CSR workflow described in the scenario.
The workflow generates one key pair on a central server and pushes both the certificate and private key to multiple target nodes over SSH.
Understanding key lifecycle boundaries is necessary to identify architectural security risks.
2
Evaluate standard PKI best practices regarding private key containment.
Private keys must never leave the boundary of the host that generated them (or its Hardware Security Module) and must be unique per endpoint.
Distributing a shared private key over the network creates a single point of failure and allows compromise of one node to impact all nodes.
3
Identify the correct administrative remediation for automated enrollment.
Each microservice gateway node should generate its own local key pair, create its own unique CSR, and receive its signed certificate individually.
Local key generation ensures proper key isolation, preserves non-repudiation, and limits the blast radius of host compromises.

Anahtar Kavram

PKI Certificate Enrollment and Key Generation Lifecycle
Tahmini Süre:2m 0s
Bu soruyu puanla