--- title: How to Apply NIST 800-53 to AI Systems | daily.dev description: Applying NIST SP 800-53 controls to AI and agentic systems requires rethinking assumptions built for human-operated infrastructure. Access control (AC-06 least... canonical: https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: How to Apply NIST 800-53 to AI Systems | daily.dev og:description: Applying NIST SP 800-53 controls to AI and agentic systems requires rethinking assumptions built for human-operated infrastructure. Access control (AC-06 least... og:url: https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy og:image: https://api.daily.dev/og/posts/OkumfHdhy.png og:image:alt: How to Apply NIST 800-53 to AI Systems og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How to Apply NIST 800-53 to AI Systems **[Teleport](https://daily.dev/sources/teleport)** · 13 min read · 0 upvotes · 0 comments ## Summary Applying NIST SP 800-53 controls to AI and agentic systems requires rethinking assumptions built for human-operated infrastructure. Access control (AC-06 least privilege, SC-07 boundary protection, SC-10 network disconnect) must extend to non-human identities like agents and pipelines. Audit controls (AU-03, AU-04, AU-10) need to capture decision chains, handle far larger log volumes, and attribute actions to specific agent instances or model versions. Configuration management (CM-02, CM-04, CM-08) must expand to cover ML frameworks, model artifacts, and data pipeline lineage. Additional controls like RA-05 vulnerability monitoring, SI-03(08) malicious code protection, and SA-11(02) threat modeling are also discussed. The piece closes with a rundown of how Teleport's identity and audit logging features map to these controls. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does NIST 800-53 least privilege (AC-06) apply to AI agents and non-human identities? Least privilege under AC-06 must extend beyond human users to cover machines, AI agents, and services across the model lifecycle. This means assigning unique, non-shared identities to training pipelines, inference services, and monitoring agents, and restricting service accounts to only the specific datasets, model artifacts, and compute resources their role requires, rather than the broadly scoped accounts common today. _Teams tightening agent permissions under AC-06 can track related security guidance on daily.dev._ ### Why is NIST 800-53 audit logging (AU-03 and AU-04) harder to implement for autonomous AI agents than for human users? Audit records for agentic systems must capture the full decision chain—triggering condition, model decision logic, action taken, and downstream effects—not just that a command was executed, as with human users. Agents also generate far higher volumes of audit data since they can process thousands of inference requests per hour, requiring fundamentally larger storage capacity planning under AU-04 than human-driven systems. _Engineers designing audit pipelines for agentic workloads follow this kind of control guidance on daily.dev._ ### What does NIST 800-53 configuration management (CM-02) need to cover for AI systems that it doesn't for traditional IT? Baseline configuration under CM-02 must expand to include the AI software stack, data and pipeline configurations, and model configuration artifacts, in addition to standard server and application versions. Most existing configuration management databases were not built to track these extra layers, so organizations need to broaden their scope to include machine learning frameworks, model architectures, and specialized compute environments. _Security leads expanding CM scope for ML infrastructure can follow this coverage on daily.dev._ ## Similar posts on daily.dev - [From guardrails to governance: A CEO’s guide for securing agentic systems](https://daily.dev/posts/from-guardrails-to-governance-a-ceo-s-guide-for-securing-agentic-systems-nwyvrgrec) · MIT Technology Review · 0 upvotes · 0 comments - [Securing AI to Benefit from AI](https://daily.dev/posts/securing-ai-to-benefit-from-ai-edbpof5yv) · The Hacker News · 1 upvotes · 0 comments - [AI security needs a shift from models to systems, researchers argue](https://daily.dev/posts/ai-security-needs-a-shift-from-models-to-systems-researchers-argue-wp2vr3azw) · CSO Online · 0 upvotes · 0 comments - [How to Govern AI Access to ERP and Financial Systems](https://daily.dev/posts/how-to-govern-ai-access-to-erp-and-financial-systems-o71tdeinm) · Security Boulevard · 0 upvotes · 0 comments - [Secure AI Workflows: The Identity and Access Management \(IAM\) Checklist](https://daily.dev/posts/secure-ai-workflows-the-identity-and-access-management-iam-checklist-5xlc1iq5y) · JFrog · 1 upvotes · 0 comments --- Tags: [#cloud](https://daily.dev/tags/cloud), [#compliance](https://daily.dev/tags/compliance), [#ai-security](https://daily.dev/tags/ai-security) [View this post on daily.dev](https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"How to Apply NIST 800-53 to AI Systems","url":"https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy"},"datePublished":"2026-08-23T12:23:00.112Z","dateModified":"2026-08-23T12:51:55.591Z","description":"Applying NIST SP 800-53 controls to AI and agentic systems requires rethinking assumptions built for human-operated infrastructure. Access control (AC-06 least...","image":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","thumbnailUrl":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cloud,compliance,ai-security","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"How to Apply NIST 800-53 to AI Systems"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/how-to-apply-nist-800-53-to-ai-systems-okumfhdhy#faq","mainEntity":[{"@type":"Question","name":"How does NIST 800-53 least privilege (AC-06) apply to AI agents and non-human identities?","acceptedAnswer":{"@type":"Answer","text":"Least privilege under AC-06 must extend beyond human users to cover machines, AI agents, and services across the model lifecycle. This means assigning unique, non-shared identities to training pipelines, inference services, and monitoring agents, and restricting service accounts to only the specific datasets, model artifacts, and compute resources their role requires, rather than the broadly scoped accounts common today. Teams tightening agent permissions under AC-06 can track related security guidance on daily.dev."}},{"@type":"Question","name":"Why is NIST 800-53 audit logging (AU-03 and AU-04) harder to implement for autonomous AI agents than for human users?","acceptedAnswer":{"@type":"Answer","text":"Audit records for agentic systems must capture the full decision chain—triggering condition, model decision logic, action taken, and downstream effects—not just that a command was executed, as with human users. Agents also generate far higher volumes of audit data since they can process thousands of inference requests per hour, requiring fundamentally larger storage capacity planning under AU-04 than human-driven systems. Engineers designing audit pipelines for agentic workloads follow this kind of control guidance on daily.dev."}},{"@type":"Question","name":"What does NIST 800-53 configuration management (CM-02) need to cover for AI systems that it doesn't for traditional IT?","acceptedAnswer":{"@type":"Answer","text":"Baseline configuration under CM-02 must expand to include the AI software stack, data and pipeline configurations, and model configuration artifacts, in addition to standard server and application versions. Most existing configuration management databases were not built to track these extra layers, so organizations need to broaden their scope to include machine learning frameworks, model architectures, and specialized compute environments. Security leads expanding CM scope for ML infrastructure can follow this coverage on daily.dev."}}]} ```