Easy ReviewDOP-C02
Security and Compliance9

Private CA

Issue private certificates and establish trust for internal clients.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

Private certificates and trust

AWS Private CAA certificate authority signs certificates and can delegate signing authority to subordinate authorities. issues private certificates for authentication and encrypted connections. A certificateA certificate binds the identity of its subject to a public key. binds an identity to a public keyA public key is the shareable key of a mathematically related public and private key pair., the shareable part of a key pair, and a certificate authority (CA) signs it. Clients decide whether to trust the chain of signatures leading to a root CAA root CA anchors trust for certificates in its hierarchy..

How it works

  1. Create a root CA and, if needed, subordinate CAs that the root or another CA signs. Configure revocation before issuing certificates.
  2. Request an end-entity certificate, a certificate for a user, device, or service, through AWS Certificate Manager (ACM) or issue one directly through AWS Private CA.
  3. Give clients the certificate chain and place the private root in their trust storeA trust store is a collection of trusted certificate authorities used to validate certificate chains., the client’s collection of trusted CA certificates.
  4. Clients can query Online Certificate Status ProtocolOCSP lets a client query an authoritative database for certificate revocation status. (OCSP) for status or download a certificate revocation listA certificate revocation list identifies revoked certificates that clients periodically download and store. (CRL), a list of revoked certificates.

Exam cues

  • If the question says clients reject an internal certificate, think private root in the client trust store, because the chain must reach a trusted root.
  • If the question says automatic renewal for a private certificate, think ACM issuance and an eligible association or export, because direct Private CA API issuance is not eligible for ACM managed renewal.
  • If the question says a certificate’s key is compromised, think revoke and check status, because clients must check OCSP or a CRL for revocation to work.
  • If the question says an exported private certificate has renewed, think export and install it again, because ACM does not deploy it to a nonintegrated service.
  • If the question says another account needs to issue from a central private CA, think AWS Resource Access Manager, because the CA administrator can share issuance access.

Remember

  • A managed CA hierarchy supports up to five CA levels.
  • A private CA is regional and cannot be copied to another Region.
  • A certificate cannot expire later than its issuing CA certificate.
  • ACM private certificates can be used with ACM integrated services.
  • ACM attempts to renew a managed private certificate 60 days before expiration. Integrated services receive the replacement without additional customer action.

Trap: A private certificate is not automatically trusted by clients. Install the private root in their trust stores.

Private certificate trust chain
123Root CASubordinate CACertificateClient
  1. The root signs a subordinate CA.

  2. The subordinate CA issues an end-entity certificate.

  3. The client validates the chain against its trusted root.

Da documentação da AWS (23)
  • AWS Private CA creates private certificate authority hierarchies and issues certificates for uses including encrypted TLS connections and authentication.
  • A private CA hierarchy has a root and can have subordinate CAs.
  • AWS Private CA supports up to five CA levels in a hierarchy.
  • Clients validate a certificate chain to a trusted root in their trust stores.
  • An organization must add its private root CA to client trust stores for validation.
  • ACM can request a private certificate from an available private CA, including a shared CA.
  • Private certificates requested through ACM can be associated with ACM integrated services.
  • Certificates issued directly through the Private CA API or exported from ACM can be installed elsewhere.
  • An ACM-issued private certificate is eligible for managed renewal if exported or associated with an AWS service.
  • A private certificate issued directly through the Private CA IssueCertificate API is not eligible for ACM managed renewal.
  • Configure OCSP or a certificate revocation list before issuing certificates to support status checking.
  • Clients must check revocation status for revocation to be effective.
  • With OCSP the client queries an authoritative revocation database.
  • A certificate revocation list is periodically downloaded and stored by clients.
  • Private CAs are regional resources and cannot be copied between Regions.
  • AWS Private CA prevents issuance of a certificate that expires later than its issuing CA certificate.
  • An X.509 certificate binds the identity of its subject, such as a user or device, to a public key.
  • A public key is the shareable key of a mathematically related public and private key pair.
  • ACM attempts to renew a managed private certificate 60 days before expiration.
  • A renewed certificate associated with an ACM integrated service replaces the old certificate without additional customer action.
  • A renewed certificate not associated with an ACM integrated service requires customer action to export and install it.
  • A CA administrator can use AWS Resource Access Manager to share CA access for issuance across accounts.
  • The recipient account is responsible for configuring ACM automatic renewal for certificates issued using a shared CA.

Flashcards

toque para virar
Resposta

·

Todos os 9 flashcards em lista

What does AWS Private CA provide for an organization's internal certificates?

A private CA hierarchy that issues certificates for authentication and encrypted TLS connections.

An internal client rejects a certificate from AWS Private CA because it cannot find a trusted root. What should the organization do?

Add the private root CA certificate to the client's trust store and provide the chain.

A team wants an AWS Private CA certificate to renew through ACM. How should it obtain and use the certificate?

Request it through ACM and export it or associate it with an AWS service; direct Private CA API issuance is not eligible for ACM managed renewal.

How many CA levels can an AWS Private CA hierarchy contain?

Up to five CA levels.

A private key is compromised. What must be in place for AWS Private CA revocation to protect clients?

Configure OCSP or a CRL before issuance and ensure clients check revocation status.

Can an AWS Private CA be copied to another Region?

No. Create a CA in each Region where it is needed.

Can an AWS Private CA issue a certificate that expires after its issuing CA certificate?

No. AWS Private CA prevents it.

An ACM-issued private certificate is exported and installed on a server outside an ACM integrated service. What happens after ACM renews it?

Export and install the renewed certificate on the server; ACM does not deploy it there automatically.

A central account owns an AWS Private CA and another account needs to issue certificates from it. What sharing mechanism can the administrator use?

Share CA access through AWS Resource Access Manager. The recipient account configures ACM automatic renewal.

Você concluiu todos os tópicos da DOP-C02!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified DevOps Engineer - Professional (DOP-C02) no Easy Review. Venha estudar também!