liveBook · Manning

Sensitive information

Also called sensitive data, confidential data, private data, private information, confidential information

Sensitive information is information whose access, disclosure, alteration, or misuse may cause harm or violate privacy, security, or confidentiality requirements.

How 12 Manning books explain it

Effective Data Analysis

Protected information is data subject to legal, regulatory, or organizational restrictions governing its collection, use, disclosure, or retention.

How it is used
Frames sensitive information as an analytics risk requiring privacy, confidentiality, and ethical handling.
How deep it goes
Defines major data categories and outlines minimization, access controls, anonymization, and re-identification safeguards.
Examples
Uses a wearable health study to explore disclosure risks, informed consent, and withdrawal requests.
What you can do after
Apply data minimization and access restrictions when planning sensitive-data analysis.

Read how Effective Data Analysis explains sensitive information →

The Art of AI Product Development

Information owned or controlled by an organization and not generally available for unrestricted public use.

How it is used
Balances the value of proprietary data in AI products against privacy, security, and customer-trust risks.
How deep it goes
Explains confidentiality classification, data flows, provider review, and safeguards, with an incident illustrating leakage consequences.
Examples
Uses internal client case studies, customer communications, and exposed chat histories and billing details as concrete examples.
What you can do after
Evaluate sensitive-data risks by tracing data flows, reviewing providers, and identifying appropriate access and encryption controls.

Read how The Art of AI Product Development explains sensitive information →

Generative AI in Action

Enterprise data is organization-owned information that may be subject to access restrictions, privacy requirements, and legal obligations.

How it is used
Uses proprietary enterprise data to ground generative AI applications in business-specific information.
How deep it goes
Outlines data ingestion and retrieval planning, while leaving access-control implementation unspecified.
Examples
Uses an authorized enterprise chatbot and identifies emails, customer feedback, and social media interactions as data sources.
What you can do after
Evaluate how enterprise data can support a chatbot while considering access, privacy, legal compliance, and production complexity.

Read how Generative AI in Action explains sensitive information →

Introduction to Generative AI, Second Edition

Proprietary data is information owned or controlled by an organization and not generally available to the public.

How it is used
Frames sensitive information as a privacy and commercial risk in LLM training and conversational prompts.
How deep it goes
Explains leakage pathways and precautions at an overview level, including the limitations of anonymization and masking.
Examples
Uses a client contract, private messages, credit card numbers, and confidential company information to illustrate exposure.
What you can do after
Evaluate and understand potential exposure before sharing information with conversational AI tools.

Read how Introduction to Generative AI, Second Edition explains sensitive information →

Practical Automation with PowerShell: Effective scripting from the console to the cloud

Sensitive data is information whose unauthorized disclosure, alteration, or loss could cause harm or compromise security.

How it is used
Protects automation inputs and environment details from disclosure or misuse while scripts run interactively or unattended.
How deep it goes
Explains identification, storage risks, execution contexts, obscurity failures, and secure retrieval options without detailing vault configuration.
Examples
Uses a SQL health check, Windows domain authorization, scheduled jobs, system context, encoded script values, and compiled executables or DLLs.
What you can do after
Apply it via SecretManagement, credential objects, vaults, and execution identities to avoid embedding sensitive values in scripts.

Read how Practical Automation with PowerShell: Effective scripting from the console to the cloud explains sensitive information →

Think Like a CTO

Sensitive data is information requiring additional protection because unauthorized access or disclosure could cause harm or violate obligations.

How it is used
Guides data classification and enterprise-specific rules for protecting information that needs additional security.
How deep it goes
Defines a sensitive-data category and develops ownership and retention questions, then illustrates transfer and logging risks without prescribing detailed controls.
Examples
Uses a client’s emailed file and clear-text passwords in API logs to show how ordinary workflows can expose protected data.
What you can do after
Practice/perform an initial review of sensitive-data categories, ownership, retention, transfer methods, and log masking.

Read how Think Like a CTO explains sensitive information →

The Design of Web APIs, Second Edition

Sensitive data is information whose inappropriate disclosure could harm individuals, systems, or organizations or violate access expectations.

How it is used
Guides decisions about which API data to expose and how to reduce disclosure risks.
How deep it goes
Defines sensitivity through disclosure harms and works through exposure and search-design decisions, while leaving classification to qualified specialists.
Examples
Uses payment card details, personal information, internal costs, and account-holder searches by name.
What you can do after
Practice/perform exposure reviews and redesign sensitive searches with POST request bodies.

Read how The Design of Web APIs, Second Edition explains sensitive information →

Fundamentals of Cybersecurity

Proprietary information is nonpublic information owned or controlled by an individual or organization as a result of its business or activities.

How it is used
Defines information whose improper access or disclosure could cause harm, linking that risk to classification and access monitoring.
How deep it goes
Defines a harm threshold and distinguishes confidentiality, but does not detail handling controls for each information type.
Examples
Shows trade secrets, customer information, health records, medical records, and contract details as examples.
What you can do after
Evaluate whether improper access or disclosure could cause harm and distinguish sensitive information from confidential information.

Read how Fundamentals of Cybersecurity explains sensitive information →

ASP.NET Core in Action, 3e

Sensitive data is information whose disclosure or misuse could harm a person, system, or organization.

How it is used
Protects application configuration secrets from accidental source-control commits during local development and production deployment.
How deep it goes
Explains secret types, storage choices, configuration loading, and security limits, but stops short of detailed encryption implementation.
Examples
Uses passwords, connection strings, API keys, appsettings.json, User Secrets, environment variables, and Azure Key Vault.
What you can do after
Operate/configure local and production secret storage without committing sensitive values to source control.

Read how ASP.NET Core in Action, 3e explains sensitive information →

AI Governance

Sensitive data is information whose nature or context calls for heightened protection, including behavioral and emotional inferences described as sensitive under GDPR Article 9.

How it is used
Frames sensitive information as a privacy and security risk when agents infer attributes, expand processing purposes, or handle authenticated sessions.
How deep it goes
Explains attribute inference and purpose creep through a scenario, then names browser isolation and monitoring controls.
Examples
Uses a medical scheduling agent that creates a health-profile tag and browser agents operating in authenticated sessions.
What you can do after
Configure browser-agent isolation, logged-out access, and real-time action logging to reduce exposure of sensitive information.

Read how AI Governance explains sensitive information →

AI for Everyday IT

Data subject to legal, organizational, or technical restrictions on access, processing, or disclosure.

How it is used
Protects restricted information when using AI services for workplace tasks.
How deep it goes
Identifies exposure risks and practical safeguards, while warning that anonymization cannot eliminate re-identification risk.
Examples
Uses support logs, medical records, financial records, employee records, and identifying details in prompts as examples.
What you can do after
Apply safeguards by checking policies, minimizing prompt details, and choosing approved AI services.

Read how AI for Everyday IT explains sensitive information →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A sensitive value is configuration or state data whose disclosure could compromise security and is therefore specially protected in displayed or stored form.

How it is used
Protects deployment credentials and runtime configuration from source repositories, routine terminal output, and recorded automation logs.
How deep it goes
Explains redaction, explicit Terraform acknowledgement, alternative storage, and the limitation that state files may remain plaintext.
Examples
Uses a container-registry password, database password, Kubernetes authentication, tokens, API keys, and the terraform output command.
What you can do after
Operate Terraform outputs and application configuration while choosing safer secret storage and avoiding unnecessary production disclosure.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains sensitive information →

Also covered in

What to know first

Related concepts

Questions about sensitive information

What is sensitive information?

Sensitive information is information whose access, disclosure, alteration, or misuse may cause harm or violate privacy, security, or confidentiality requirements.

Which Manning books explain sensitive information?

Effective Data Analysis, The Art of AI Product Development, Generative AI in Action, Introduction to Generative AI, Second Edition, Practical Automation with PowerShell: Effective scripting from the console to the cloud, Think Like a CTO, The Design of Web APIs, Second Edition, Fundamentals of Cybersecurity and 4 more.

What should I know before learning sensitive information?

Manning books that teach sensitive information usually introduce language model, GDPR, personal data and security first.

What is the difference between sensitive information and log?

Sensitive information is information whose access, disclosure, alteration, or misuse may cause harm or violate privacy, security, or confidentiality requirements. A log is a time-ordered record of events, messages, or activity generated by a system or process.

What kinds of sensitive information are there?

Kinds of sensitive information include personal data, password authentication and private health information.

What is sensitive information a kind of?

Sensitive information is a kind of data. Data is recorded or represented information, observations, measurements, or values that can be stored, processed, communicated, or interpreted.

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.