Sensitive information
Sensitive information is information requiring protection because its unauthorized access, disclosure, alteration, or misuse could cause harm or violate obligations.
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
- Guides decisions about whether and how to analyze personal data without exposing people or organizations to avoidable harm.
- How deep it goes
- Defines major data categories and gives handling practices, consent questions, and re-identification cautions without a technical security implementation.
- Examples
- Uses a wearable-device health study, identifying and financial data categories, and a biased résumé-ranking model.
- What you can do after
- Practice/perform a necessity check, limit collection and access, plan retention, and raise consent and disclosure risks before 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
- Frames proprietary data as both a source of more useful AI outputs and a privacy risk requiring controlled access.
- How deep it goes
- Provides a practical review of data flows, provider policies, encryption, access controls, and audits without implementation instructions.
- Examples
- Uses internal case studies for AI-generated content, an enterprise-client data leak, and a ChatGPT chat-history disclosure.
- What you can do after
- Evaluate/understand where confidential data enters an AI workflow and which access, provider, and privacy safeguards warrant review.
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 data to make enterprise chatbots answer organization-specific questions while treating access, privacy, and legal compliance as deployment concerns.
- How deep it goes
- Outlines data selection, ingestion, indexing, and production planning, but does not specify access-control rules or privacy implementation details.
- Examples
- Uses an authorized internal chatbot and unstructured sources such as emails and customer feedback as concrete cases.
- What you can do after
- Evaluate/understand how to prepare proprietary data for an enterprise chatbot and where governance and production engineering enter the workflow.
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 privacy and commercial risks when sensitive information enters LLM training data or user prompts.
- How deep it goes
- Explains exposure pathways and practical precautions at a high level, without implementation steps for privacy protections.
- Examples
- Uses a client contract entered into a chatbot, retained conversations, and personal details reproduced from training data.
- What you can do after
- Practice/perform cautious LLM use by limiting confidential inputs and checking workplace rules, privacy disclosures, and user choices.
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.
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.
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 →
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.
Related concepts
- personal dataincludes · Personal data is information relating to an identified or identifiable person, directly or indirectly, alone or in combination with other information.
- fine-tuningused by · Fine-tuning is adapting a pretrained machine-learning model by training it further on targeted data or objectives for a task, domain, or behavior.
- datakind of · Data is represented information, observations, measurements, or other values that can be stored, processed, transmitted, analyzed, or interpreted.
- password authenticationincludes · Password authentication is an authentication method that verifies a claimed identity or access by checking a supplied secret password or passphrase.
- retrieval-augmented generationused by · Retrieval-augmented generation is a technique that retrieves relevant information from external sources and supplies it as context to a generative model when producing an output.
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.