liveBook · Manning

Certification authority

A certification authority is a trusted entity that verifies identities and issues digitally signed certificates binding public keys to identities or domains.

How 8 Manning books explain it

Real-World Cryptography

A certificate authority is an entity that issues and digitally signs certificates binding public keys to identities or domains.

How it is used
Establishes server identity during TLS authentication by linking a domain to a public key through signed certificates.
How deep it goes
Explains trust stores, root and intermediate CAs, leaf certificates, signatures, and impersonation risks without detailing CA operations.
Examples
Uses a Google certificate chain showing GlobalSign, GTS CA 101, and a *.google.com leaf certificate.
What you can do after
Evaluate a TLS certificate chain by tracing signatures from a website certificate to a browser-trusted root.

Read how Real-World Cryptography explains certification authority →

Software Security for Developers

A local certificate authority is a privately operated certificate authority that issues certificates within an organization's or development environment's trust boundary.

How it is used
Establishes trusted identities for public websites, internal services, and development systems through signed X.509 certificates.
How deep it goes
Traces issuance from key pair and CSR through validation, signing, trust installation, expiry, and revocation without covering private-key protection practices in depth.
Examples
Uses github.com certificate-chain inspection, OpenSSL verification, internal microservices, self-signed certificates, and operating-system trust-store installation.
What you can do after
Operate/configure a local CA, install its trust anchor, issue internal certificates, and diagnose chain-validation failures with OpenSSL.

Read how Software Security for Developers explains certification authority →

ASP.NET Core in Action, 3e

A certificate authority is a trusted entity that issues or signs digital certificates to attest to the identity of certificate holders.

How it is used
Establishes browser trust in HTTPS certificates by signing certificates and linking them to trusted root certificates.
How deep it goes
Explains certificate chains, root trust, browser updates, and domain validation, but not provider-specific issuance procedures.
Examples
Uses development certificate warnings and production domain-ownership validation as concrete examples.
What you can do after
Evaluate browser trust decisions and recognize why production certificates require domain-ownership proof.

Read how ASP.NET Core in Action, 3e explains certification authority →

Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools

A certificate authority is a trusted entity that issues and signs digital certificates after validating certificate requests.

How it is used
Supports script signing by establishing who issued a certificate and whether the signing identity is trusted.
How deep it goes
Explains commercial, internal, and self-signed issuance choices, but defers detailed PKI administration.
Examples
Uses commercial vendors, Active Directory Certificate Services, and a PowerShell self-signed certificate command.
What you can do after
Apply the PowerShell PKI module to create a test certificate and select an appropriate CA for deployment.

Read how Learn PowerShell Scripting in a Month of Lunches, Second Edition: Write and organize scripts and tools explains certification authority →

Logs and Telemetry

A certificate authority is a trusted entity that issues and validates digital certificates and maintains their revocation records.

How it is used
Protects observability data transmitted through network-based Fluent Bit plugins.
How deep it goes
Configures CA paths and TLS verification in an HTTP input, but stops short of explaining certificate issuance or revocation workflows.
Examples
Uses a Fluent Bit HTTPS input with CA directory, optional CA file, private key, and verification settings.
What you can do after
Operate/configure a Fluent Bit HTTP input with a CA path and explicit TLS verification settings.

Read how Logs and Telemetry explains certification authority →

Build Python Web Apps with Streamlit

A certificate authority is a trusted entity that validates identities and digitally signs certificates for them.

How it is used
Secures a deployed web app by establishing browser trust for HTTPS.
How deep it goes
Explains certificates, domain verification, DNS validation, and ACM renewal, but stops short of certificate internals.
Examples
Uses an Elastic Beanstalk app, a custom domain, ACM, and DNS CNAME records as the practical certificate workflow.
What you can do after
Operate/configure AWS Certificate Manager to request and validate a public certificate for a custom app domain.

Read how Build Python Web Apps with Streamlit explains certification authority →

Google Anthos in Action

A certificate authority is a trusted entity that issues and signs digital certificates.

How it is used
Secures service-to-service communication by issuing workload identities within an Istio mesh.
How deep it goes
Defines certificate trust and explains self-signed, administrator-specified, and delegated CA configurations.
Examples
Uses Istio’s default self-signed root and enterprise deployments with existing root or delegated CA credentials.
What you can do after
Operate Istio identity provisioning by selecting self-signed, administrator-specified, or delegated CA credentials.

Read how Google Anthos in Action explains certification authority →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

A certificate authority is a trusted entity that issues and verifies digital certificates.

How it is used
Supports website authentication and secure HTTPS connections by issuing and verifying digital certificates.
How deep it goes
Defines certificate issuance, verification, browser checking, and warning behavior without detailing certificate-management internals.
Examples
Uses Chrome’s padlock indicator and certificate details as the concrete verification example.
What you can do after
Evaluate website identity through browser certificate indicators and recognize warnings when verification fails.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains certification authority →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.