<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Business on New England Cyber</title>
    <link>https://newenglandcyber.org/tags/business/</link>
    <description>Recent content in Business on New England Cyber</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2024–2026 all rights reserved.</copyright>
    <lastBuildDate>Sun, 02 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://newenglandcyber.org/tags/business/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI Is an Identity, Not Just a Technology</title>
      <link>https://newenglandcyber.org/posts/ai-is-an-identity-not-just-a-technology/</link>
      <pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://newenglandcyber.org/posts/ai-is-an-identity-not-just-a-technology/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;AI Is an Identity, Not Just a Technology&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is the first post in a twelve-part series about a simple shift: organizations should treat AI not only as software, but as something that performs work. That makes AI a business conversation, not just a technology or cybersecurity one. Before AI is connected to everything, invited into every workflow, or handed the digital equivalent of a master key, it needs a role, an owner, and boundaries.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
