Principle of least privilege

As explained in Generative AI in Action

The principle of least privilege is a security principle that grants a system or component only the minimum access required to perform its intended functions.

The principle of least privilege grants an LLM or system component only the minimum access required for its intended functions. In prompt-injection defenses, privilege controls limit access to backend systems through the application and system APIs. section 13.2.1

Apply the principle with layered controls:

• Assign identity-based authentication or API tokens for expandable capabilities such as data access and function-level permissions. section 13.2.1
• Require user confirmation before sensitive operations so indirect injections cannot act without explicit agreement. section 13.2.1
• Audit and detect attempted injections with application logging, while treating the LLM as unreliable. section 13.2.1

Figure 13.2 Prompt injection threats [4]

Use the threat diagram to relate excessive model access to possible prompt-injection consequences. section 13.2.1

How Generative AI in Action covers it

How deep it goes

Defines minimum required access and connects it to privilege control, authentication, and function-level permissions without implementation detail.

Examples

Uses API tokens, backend-system permissions, sensitive-operation confirmations, and prompt-injection threat diagrams.

What you can do after

Apply it through privilege controls, identity-based authentication, confirmation gates, and audited API access.

How it connects

Connects prompt injection with backend APIs, authentication, human confirmation, ChatML, and application logging.

liveBookmanning.com

Read Generative AI in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformThe principle of least privilege grants each user or service account only the minimum permissions required to complete its tasks.
• 

  liveBookmanning.com
  100 SQL Server Mistakes and How to Avoid ThemLeast privilege is a security principle that grants each user only the permissions required for their duties.
• 

  liveBookmanning.com
  Acing the Certified Kubernetes Administrator Exam, Second EditionThe principle of least privilege is a security practice of granting only the permissions required for an identity or component to perform its duties.
• 

  liveBookmanning.com
  MongoDB 8.0 in Action, Third EditionThe principle of least privilege is a security practice of granting each identity only the permissions necessary for its tasks.
• 

  liveBookmanning.com
  Authorization in ActionThe principle of least privilege requires each subject to receive only the access necessary to perform its authorized tasks.
• 

  liveBookmanning.com
  AI Agents in Action, Second EditionLeast privilege is a security principle that grants each user, process, or agent only the minimum permissions needed for its tasks.
• 

  liveBookmanning.com
  Grokking Web Application SecurityLeast privilege is a security principle in which each software component and process receives only the permissions required to perform its intended functions.
• 

  liveBookmanning.com
  Amazon Web Services in Action, Third Edition: An in-depth guide to AWSLeast privilege is a security principle that grants an identity only the permissions required for its intended tasks.
• 

  liveBookmanning.com
  .NET in Action, Second EditionLeast privilege is an authorization principle that grants an identity only the permissions required for its tasks.
• 

  liveBookmanning.com
  Build Financial Software with Generative AI (From Scratch)The principle of least privilege is a security practice of granting only the permissions necessary to perform required work and removing elevated permissions when they are no longer needed.
• 

  liveBookmanning.com
  Data-Driven CybersecurityThe security principle and access-control practice of granting each subject only the minimum permissions required to perform authorized tasks.
• 

  liveBookmanning.com
  Practical Automation with PowerShell: Effective scripting from the console to the cloudThe principle of least privilege is a security practice of granting an identity or process only the permissions required for its intended operations.
• 

  liveBookmanning.com
  Secure APIsA security principle that grants each user, service, or process only the minimum access required for its authorized tasks.
• 

  liveBookmanning.com
  PostgreSQL Mistakes and How to Avoid ThemThe principle of least privilege is a security practice of granting each account only the permissions required for its tasks.
• 

  liveBookmanning.com
  Azure SecurityLeast privilege is an access-control principle that grants only the permissions necessary for a task and only for the required duration.
• 

  liveBookmanning.com
  GitHub Actions in Action: Continuous integration and delivery for DevOpsThe principle of least privilege is a security practice of granting only the minimum permissions required for an actor or process to perform its task.

Compare how 17 books explain principle of least privilege →

Related concepts

• permissionconfigures · A permission is an authorization specifying whether an identity or process may perform an action on or access a resource.
• authorizationconfigures · Authorization is the determination and enforcement of rules governing which subjects may access resources or perform operations.
• service accountconfigures · A service account is a non-human identity or account used by software, services, or automated processes to authenticate and access authorized resources.
• scopeimplemented by · Scope is a defined boundary specifying which entities, activities, resources, or conditions are included or governed in a particular context.
• sysadmin fixed server rolecontrasts with · The sysadmin fixed server role is a SQL Server fixed server role whose members have unrestricted administrative permissions over the instance.
• blast radiusaddresses · Blast radius is the scope of systems, components, data, users, or functionality that may be affected by a failure, change, or other disruptive event.

This explainer was generated by Manning's knowledge graph from the text of Generative AI in Action. The section links point to the parts of the book it draws on.