liveBook · Manning

Secret management

Secret management is the practice of securely handling sensitive values throughout their lifecycle, including their storage, access, distribution, retrieval, and rotation.

How 8 Manning books explain it

Effective Platform Engineering

A secrets manager is a system that securely stores, controls access to, and rotates sensitive credentials and configuration values.

How it is used
Supplies pipelines and deployment workflows with credentials through a central platform capability.
How deep it goes
Works through credential bootstrap, pipeline retrieval, and overlapping-key rotation; leaves secrets-service internals unspecified.
Examples
Uses a CircleCI context holding a secrets-access credential and an AWS service-account pipeline that stores and rotates keys.
What you can do after
Operate/configure a pipeline to retrieve centrally stored credentials and take over rotation after a manual first-time bootstrap.

Read how Effective Platform Engineering explains secret management →

Data Pipelines with Apache Airflow, Second Edition

A secrets manager is an external system that securely stores and provides sensitive values such as credentials and keys.

How it is used
Keeps Airflow connections and variables available to tasks while obtaining their secrets from central storage.
How deep it goes
Explains backend configuration, secret paths, required keys, and a DAG lookup; does not develop secret rotation procedures.
Examples
Uses a Vault-backed HttpOperator connection and contrasts production secret storage with local AWS credential-file testing.
What you can do after
Operate/configure it: configure an Airflow secrets backend and store connection details under the expected path and key.

Read how Data Pipelines with Apache Airflow, Second Edition explains secret management →

Building Web APIs with ASP.NET Core

Visual Studio Secret Manager is a development tool that stores application secrets outside the project source tree and loads them through user-secrets configuration.

How it is used
Secures connection strings and credentials during development.
How deep it goes
Shows how to open Secret Manager and add its project identifier, without detailing further configuration steps.
Examples
Uses a SQL Server connection string for the board-game API’s database.
What you can do after
Configure development credentials with Visual Studio Secret Manager and use the DefaultConnection key in database configuration.

Read how Building Web APIs with ASP.NET Core explains secret management →

Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu

A secret manager is software that securely stores, controls access to, and retrieves sensitive values such as credentials and API keys.

How it is used
Keeps deployment credentials and API keys out of plaintext inputs while making them available to Terraform or workloads.
How deep it goes
Explains identifier-based retrieval and compares Terraform data sources with direct workload retrieval, including the risk of secrets entering state.
Examples
Shows AWS, Vault, and Azure Terraform lookups and considers updating an API key across hundreds of projects.
What you can do after
Apply it via Terraform data sources or configure an orchestrator to retrieve secrets without passing their values through Terraform.

Read how Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu explains secret management →

.NET in Action, Second Edition

Secret Manager is a .NET development tool for storing and retrieving user secrets outside an application's project files.

How it is used
Keeps local-development secrets out of project configuration while making them available to the application.
How deep it goes
Shows initialization, storing values, and retrieving a connection string through configuration, while deferring container secret exposure.
Examples
Uses a Catalog connection string and Azure AD client and tenant IDs as stored values.
What you can do after
Operate/configure Secret Manager by initializing a project, setting named values, and reading a connection string through configuration.

Read how .NET in Action, Second Edition explains secret management →

AI Governance

Secret management is the secure storage, controlled use, and periodic replacement of credentials, keys, and other sensitive authentication material.

How it is used
Protects GenAI systems from credential exposure by centralizing API keys and tokens within a Zero Trust architecture.
How deep it goes
Places centralized secret storage across the system flow and names vault tools, but gives no implementation procedure.
Examples
Cites leaked xAI, OpenAI, and Azure OpenAI credentials, alongside AWS Secrets Manager and HashiCorp Vault.
What you can do after
Operate/configure centralized storage for API keys and tokens using AWS Secrets Manager or HashiCorp Vault.

Read how AI Governance explains secret management →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

A secrets manager is a system for securely storing, controlling access to, and rotating sensitive credentials such as passwords.

How it is used
Separates credential storage and rotation from infrastructure configuration and delivery pipelines.
How deep it goes
Explains storage, variable passing, rotation, and pipeline exposure, but stops short of naming a specific product implementation.
Examples
Uses expiring load-balancer certificates, database passwords, API credentials, private keys, and pipeline logs as operational examples.
What you can do after
Operate/configure IaC and delivery pipelines without hardcoding, exposing, or manually embedding sensitive credentials.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains secret management →

Grokking Software Architecture

Secrets management is the practice of securely storing, controlling access to, distributing, and rotating sensitive authentication data such as passwords and database credentials.

How it is used
Protects database access credentials by keeping connection strings and passwords out of application source code.
How deep it goes
Recommends key vaults or environment variables and shows the risks of hardcoding, without detailing setup.
Examples
Uses committed configuration and a Python database connection with hardcoded admin credentials as unsafe examples.
What you can do after
Configure database credentials outside source code using a key vault or environment variables.

Read how Grokking Software Architecture explains secret management →

Also covered in

What to know first

Related concepts

Questions about secret management

What is secret management?

Secret management is the practice of securely handling sensitive values throughout their lifecycle, including their storage, access, distribution, retrieval, and rotation.

Which Manning books explain secret management?

Effective Platform Engineering, Data Pipelines with Apache Airflow, Second Edition, Building Web APIs with ASP.NET Core, Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu, .NET in Action, Second Edition, AI Governance, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform and Grokking Software Architecture.

What should I know before learning secret management?

Manning books that teach secret management usually introduce authentication, deployment pipeline, authorization and credential first.

What is the difference between secret management and environment variable?

Secret management is the practice of securely handling sensitive values throughout their lifecycle, including their storage, access, distribution, retrieval, and rotation. An environment variable is a named value supplied through a process's execution environment and made available to the process at runtime.

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.