
Shadow AI is any use of AI that happens outside approved, governed channels. It includes browser chat tools, desktop apps, browser extensions, coding assistants and AI agents that employees adopt on their own, often with good intentions and personal accounts. It is the AI version of shadow IT, and it is growing quickly.
IBM and the Ponemon Institute's 2026 Cost of a Data Breach study found shadow AI involved in 43% of the breaches studied, up from 20% the year before [1][2]. Breaches involving shadow AI averaged $5.39 million, compared with a record global average of $4.99 million across all breaches [3]. Among organizations with an AI-related incident, 92% lacked proper AI access controls [3]. The prior edition found that 63% of breached organizations had no AI governance policy [4].
The behavior behind these numbers is ordinary. One 2025 workplace study reported that 77% of employees paste data into generative AI prompts, and 82% of those pastes came from personal accounts [5]. Shadow AI breaches have also been reported to take longer to detect, 247 days versus 241 on average [6].
Whether you run a firm in Central Jersey, Newark, Jersey City or the wider NJ and NYC metro area, two local signals are worth knowing.
The state is already drawing the line. New Jersey's own guidance for state employees, Joint Circular 25-OIT-001, issued by the Office of Information Technology and the NJ Cybersecurity and Communications Integration Cell (NJCCIC), says only tools approved through their review processes may be used for transcription and summarization when sensitive content is involved [7]. State employees are also told not to put sensitive or private information, such as personally identifiable information, into AI prompts [8]. The state went further and built the NJ AI Assistant, a protected environment, because generative AI software often captures inputs to improve its models, which could expose internal data [9]. The pattern is the one to copy: approve, restrict and provide a safe option. This guidance covers state employees, not private companies, but it shows what a careful approach looks like.
The New Jersey Data Privacy Act raises the stakes for customer data. The Act took effect on January 15, 2025, and applies to businesses and nonprofits that meet its thresholds [10][11]. Among other duties, covered businesses must use reasonable data security practices, conduct data protection assessments for higher-risk processing such as profiling and sensitive data, and keep records of those assessments [11]. If employees paste customer personal data into an unapproved AI tool, it becomes much harder to show that those duties are being met. The Act is enforced through the state, with rules to be issued by the Division of Consumer Affairs, and it has no private right of action [10]. Whether it applies to you is a question for your counsel.
Build an inventory of AI tools, extensions, desktop apps, coding assistants and agents, not just the approved list. Include the tokens and service accounts they use, since unapproved agents can reach systems through credentials no one is tracking [12]. Combine a short survey of your teams with a review of network and SaaS logs.
Write a one-page acceptable use policy. Sort data into a few classes (public, internal, confidential, regulated) and state which tools may handle each. Be explicit about personal accounts, which typically have no enterprise retention controls, audit trail or contractual data protections [6]. The NIST AI Risk Management Framework is a vendor-neutral reference for structuring this work [13].
A policy alone will not stop a rushed paste. Add access controls, data classification and monitoring so the rules are enforced inside the workflow. Prioritize the places customer personal data lives, because shadow AI incidents disproportionately expose it and cost more per record [14].
Blocking AI outright rarely works, because the productivity benefits are real and people find workarounds. Offer approved, governed tools that are as easy to use as the risky ones, and explain why the rules exist. New Jersey's AI Assistant for state staff is a public-sector example of this approach [9].
Shadow AI is the use of AI tools by employees without the organization's approval, visibility or governance. Examples include personal chatbot accounts, unapproved browser extensions and coding assistants.
IBM's 2026 Cost of a Data Breach study found shadow AI in 43% of breaches studied, up from 20% a year earlier [1][3].
Breaches involving shadow AI averaged $5.39 million in IBM's 2026 data, compared with $4.99 million for breaches overall [3].
New Jersey has issued AI guidance for state employees, Joint Circular 25-OIT-001 [7]. For private businesses, the New Jersey Data Privacy Act sets data security and assessment duties for covered organizations [10][11]. Ask your counsel whether it applies to you.
Bans alone rarely work because people find workarounds. A better approach combines clear rules, technical controls and approved tools that are easy to use.
Start with an inventory. You cannot govern tools you do not know about, so identify which AI tools, extensions and agents your teams actually use.
AI adoption does not have to mean giving up visibility. The SamurAI's AI Governance capability helps New Jersey organizations control what they deploy and trust what they build, with practical policies, controls and oversight designed around how your teams really work.
Not sure which AI tools are active in your environment today? That is a good place to begin. Book a consultation with our Bridgewater, NJ team to map your AI footprint, or learn more about AI Governance.

To govern AI in Connecticut, follow four steps: inventory every AI system you use, classify each by ...

A lower price per token doesn’t guarantee a lower AI bill. What you pay depends on how many tokens a...

For years, buying cyber insurance was treated as a checkbox: fill out a questionnaire, pay the premi...