<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on Accession1</title>
    <link>https://accession.one/blog/</link>
    <description>Recent content in Blog on Accession1</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 30 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://accession.one/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The answer to agentic AI security can&#39;t be adding more tools</title>
      <link>https://accession.one/blog/agentic-ai-security-cant-be-adding-more-tools/</link>
      <pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://accession.one/blog/agentic-ai-security-cant-be-adding-more-tools/</guid>
      <description>&lt;p&gt;The security risks of autonomous AI agents have a map now.&#xA;The &lt;a href=&#34;https://labs.cloudsecurityalliance.org/research/csa-research-note-cisa-agentic-ai-five-risk-framework-implem/&#34;&gt;CISA Agentic AI Five-Risk Framework&lt;/a&gt; sorts them into five categories: privilege, design and configuration, behavioral, structural, and accountability.&#xA;It&amp;rsquo;s a good map, but the market&amp;rsquo;s answer is turning into a second problem, a fast-growing collection of agent-specific security tools, one silo per risk category, each managed on its own, and nobody connecting them.&#xA;The five categories are the challenge to tackle, and the five silos are what IT and security teams will have to live with.&#xA;Our feeling, from talking to the teams who run these stacks, is that operating one can be overwhelming, and just adding more tools isn&amp;rsquo;t helping.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why the agentic organization needs context-aware access control</title>
      <link>https://accession.one/blog/agentic-organization-context-aware-access-control/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://accession.one/blog/agentic-organization-context-aware-access-control/</guid>
      <description>&lt;p&gt;Many organizations adopting AI agents seem to sit somewhere between a few pilots and a handful of agents doing real work inside one department.&#xA;The agentic organization, where people and agents share work end to end, is further out, and the distance is usually described as a question of models, data, and tooling.&#xA;I think the harder part is the boundaries inside the organization itself.&#xA;Some of the slowest processes today are the ones that cross teams, functions, and legal entities, and an agent that gets stuck at the same boundaries a person does is unlikely to make them much faster.&#xA;So before access control can let agents through, it has to understand where those boundaries are and why they exist.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How organizational structure shapes dynamic access management</title>
      <link>https://accession.one/blog/organizational-structure-agentic-ai-access-governance/</link>
      <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://accession.one/blog/organizational-structure-agentic-ai-access-governance/</guid>
      <description>&lt;p&gt;Organizational structure has meaning.&#xA;It shapes how decisions flow, who holds authority, and how quickly change can happen, so when you layer agentic AI on top of an existing organizational model, the fit is either natural or deeply awkward.&lt;/p&gt;&#xA;&lt;p&gt;Many teams treat AI adoption as a technology problem, but it&amp;rsquo;s at least as much an organizational one.&#xA;The structure you already have decides which access models work, which approval patterns break, and whether agents become accelerators or bottlenecks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why self-service provisioning becomes essential in the agentic AI era</title>
      <link>https://accession.one/blog/why-self-service-access-essential-agentic-ai-era/</link>
      <pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://accession.one/blog/why-self-service-access-essential-agentic-ai-era/</guid>
      <description>&lt;p&gt;Access management was built for people who request access, wait for an approval, and work around the delay in the meantime.&#xA;Agentic AI removes every part of that assumption, because an agent doesn&amp;rsquo;t wait, doesn&amp;rsquo;t work around anything, and doesn&amp;rsquo;t apply judgment before it acts.&lt;/p&gt;&#xA;&lt;p&gt;Self-service provisioning has been sold as a productivity improvement for a long time, and for a long time that was fair.&#xA;In the agentic era it turns into an operating requirement, and the question worth asking is whether an organization can keep its current delivery expectations without it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Non-human identities aren&#39;t new, but agentic AI raises the stakes</title>
      <link>https://accession.one/blog/non-human-identities-not-new-agentic-ai-least-privilege/</link>
      <pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://accession.one/blog/non-human-identities-not-new-agentic-ai-least-privilege/</guid>
      <description>&lt;p&gt;The problems with non-human identities didn&amp;rsquo;t start with AI agents.&#xA;Security teams have managed service accounts, bots, scripts, and pipeline credentials for years, so what changed isn&amp;rsquo;t the category but the operating profile: more identities act on more target systems, more often, with less human pause between decision and impact.&#xA;The category is old.&#xA;The tempo is not.&lt;/p&gt;&#xA;&lt;p&gt;This is one of the questions we spend our time on at Accession1, and we treat it as a design constraint rather than a thought experiment.&#xA;Scaling organizations have always hit the same failure modes as teams and target systems multiply, and agentic AI doesn&amp;rsquo;t invent new ones.&#xA;It brings them forward, and it brings them to smaller organizations than before.&#xA;Our working assumption is that the patterns that held up will keep holding up: task-scoped least privilege, a recorded owner for every identity, and just-in-time elevation for bounded actions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
