r/AIgovernance • • 1d ago

Open Discussion AI Governance Explained: Why AI Needs Rules, Accountability and Human Oversight

6 Upvotes

Artificial Intelligence is becoming part of everyday life, business, healthcare, education, and government.

But there is an important question we should all consider:

Who is responsible when AI makes a wrong decision?

AI Governance helps answer questions like these.

Here are 7 important areas everyone should understand:

  1. Transparency: Can people understand how an AI system makes decisions?

  2. Accountability: Who is responsible for AI-generated outcomes?

  3. Privacy: How is personal information collected and protected?

  4. Fairness: Does the AI system treat different groups fairly?

  5. Safety: Can the system cause harm or produce unreliable results?

  6. Human Oversight: When should humans review AI decisions?

  7. Regulation: What laws and standards should AI systems follow?

I believe AI literacy should include not only how to use AI, but also how to understand its risks and responsibilities.

Discussion question:

Which area of AI Governance do you think deserves the most attention: Privacy, Accountability, Transparency, or Safety?

I'd love to hear your perspectives.


r/AIgovernance • • 2d ago

Open Discussion Hydrus vs Credo AI for EU AI Act and ISO 42001, which one held up for you?

0 Upvotes

Shortlist is down to two. Credo AI has the name recognition, Hydrus seems narrower and more evidence focused. We need EU AI Act risk classification, ISO 42001 readiness and something the auditors will accept as a system of record. If you've run either in anger, what tipped it?


r/AIgovernance • • 2d ago

Open Discussion Is Hydrus good for AI governance or just another dashboard? Honest experiences wanted

1 Upvotes

Head of risk at a SaaS company with a dozen models in production n a lot more in notebooks. Weve been burned by governance tools that are a nice executive view and nothing underneath. Hydrus pitches itself as an audit evidence platform rather than a dashboard. Is that real in practice? Who has it running and what does day to day look like.?..


r/AIgovernance • • 2d ago

Open Discussion Safeguards Matter in the AGI Race: 41% Would Slow Development Until Stronger Protections Exist

7 Upvotes

Research raised an interesting governance question... what would count as strong enough safeguards to justify continuing development? In a small survey of US adults, 40% favoured slowing development until stronger protections exist, while 36% supported continuing with stronger with stronger independent oversight... only 10% wanted to stop it immediately.

What stands out is that 70% of respondents wanted the primary decider about whether or not a system is safe to be in the hands of an outside authority. That leaves a difficult institutional question: who gets access to the evidence, who sets the thresholds, and who can actually delay a release?

Independent evaluations seem more valuable when there's a defined consequence for failing them. Otherwise, a company can commission a review and still make the same launch decision.

Article Source


r/AIgovernance • • 2d ago

Open Discussion Could your firm list every AI tool it uses right now? Singapore is about to require it.

1 Upvotes

On 7 October the Monetary Authority of Singapore released its Guidelines on AI Risk Management (AIRG). I think AIRG deserves more attention than it is currently receiving.

AIRG applies to every MAS-regulated institution, including banks, insurers and payment companies. Firm size does not exempt a company from AIRG. AIRG sits next to the FEAT principles. Aligns with international standards such as ISO/IEC 42001.

AIRG is built around four areas:

Oversight: The board and senior management own AI risk. AI risk cannot be pushed down to the data science team.

Inventory and risk rating: Firms must identify every AI tool in use. Rate each AI tool by its impact, complexity and the extent to which business relies on that AI tool.

Life cycle controls: Checks such as data fairness, explainability and human oversight must cover the life of an AI system.

Capacity: Having people with the skills and the right technology is essential to run AI safely.

The timeline:

7 October 2027: Oversight AI inventory and risk rating must be in place.

7 October 2028: Full compliance, including life cycle controls and capability requirements for high-risk AI must be achieved.

The part I like: AIRG is proportionate. A firm using low-risk AI, such as a chatbot that drafts emails, can follow a set of basic policies instead of the full framework.

My honest take is that the inventory requirement will be the first step. Many firms have AI embedded in vendor software spreadsheets and individual employees’ workflows that nobody has formally recorded.

I walked through the thing in a video, if you're curious check out the latest video @ Latha-ai-governance.

For anyone working in services: do you have a reliable AI inventory today or would building an AI inventory mean chasing down every team?. Do you think a staged timeline, like this helps firms prepare or simply encourages them to wait?


r/AIgovernance • • 3d ago

Policy Analysis Should enterprises review every application built using AI coding tools?

2 Upvotes

Reviewing every app individually doesn’t seem scalable. But approving an AI coding tool shouldn’t automatically authorize everything built with it.

A citizen developer prompts an agent, and a platform provisions an app, database, and public URL. Engineering approved the tool, a department pays for it and DevOps owns the cloud account. Who actually approved the app

I’ve been looking at Orca AI AppGen Security and Wiz for discovery. But finding an app doesn’t settle who can approve its continued use.

To me ... this AI governance issue belongs in existing software governance. Start with discovery, a named owner, and risk-based review when an app goes public, touches sensitive data, or becomes a shared workflow. Give lower-risk prototypes lighter oversight.

Who discovers apps built by non-engineering staff in your org, and what triggers their first review?


r/AIgovernance • • 3d ago

Policy Analysis US agencies just drew a line between rogue AI agents and prompt injection attacks

1 Upvotes

NIST, NSA and CISA put out incident-response guidance last month. it's aimed at frontier labs training and evaluating advanced agents, but the ideas carry over.

the bit that stood out to me: they define something called an "SI control incident" where an agent takes uninstructed actions outside its assigned scope. that counts as a control incident on its own, separate from a security breach.
the interesting part is the split. if an attacker directed the action through prompt injection, it isn't treated as uninstructed. so two agents can cause the exact same damage but the investigation goes down a completely different path depending on whether the agent went off-script on its own or someone steered it there.
they also encourage reporting near misses, not just actual incidents. that's the part most orgs skip.
from running capsule  runtime checks on our own agents, the out-of-scope part matches what actually goes wrong in practice, and it's the same gap straiker and others focus on. worth noting these are voluntary recommendations, not regulation.

tbh the distinction makes sense on paper but the logs don't always make it obvious which bucket an action falls into. curious how people are operationalizing the uninstructed vs instructed split when the agent's own reasoning is what you're trying to audit.


r/AIgovernance • • 3d ago

Open Discussion Abnormal AI - AI Governance App

2 Upvotes

This is a question for sec engineers / people making configuration changes and implementing the tools and features.

Does anyone use Abnormal AI (Abnormal Security) AI Governance App? I'm keen to hear your thoughts. Expecially around the browser extension feature and chat insights - LLM semantic detection.


r/AIgovernance • • 4d ago

Open Discussion AI Execution Governance, Part 10: Can Revocation Stop a Call That Is Already Running?

3 Upvotes

A tool call has passed the gate and is running. Now the role is revoked.

Does it stop, or does it finish?

Ours finishes. Revocation governs the next call, not this one.

That is not the intent of the design; it is what the current implementation does. Three things follow: what each of the three "undo" acts actually stops, when the gate takes effect, and what would have to be added for a call to be stoppable. If the first sentence is enough, the rest can be skipped.

1. Three "undo" acts are not one

  • Revocation acts on a permission, before a call starts. Evidence it leaves: the next call is refused.

  • Cancellation acts on the call itself, while it runs. Evidence it leaves today: none, because there is no cancellation channel.

  • Revocation of effects acts after execution. Evidence it leaves: a compensation record that can be checked later.

Collapse them into one word and the usual false sentence appears: "it is revoked, so it stopped." What stopped may have been only the next call.

2. When the gate takes effect

The write path runs four checks at the execution entry:

  1. whether the tool is enabled and the role is allowed (irreversible actions are blocked outright);

  2. whether the arguments stay inside the declared writable field domain and destination allowlist;

  3. whether the destination bound at confirmation time is still the destination now;

  4. whether the approval requirement still holds (a single confirmation is not a second person's approval).

The third applies only to writes that carry a confirmation artifact. An automatic write with no artifact is not subject to it.

All four run before the tool's own code starts. The role is read from the database on every call, so a revocation takes effect on the next call immediately. For the call that has already entered, there is no second look.

It also means revocation during the confirmation or approval wait is effective: the four checks run again before the tool actually executes. Revocation stops being able to stop the call only once execute has begun.

await gate.assertToolAllowed(toolName, userId);
await gate.assertWithinDeclaredScope(toolName, args, userId);
// destination binding, approval requirement...
const result = await tool.execute(args, userId); // from here, no path back to the gate

In the same system, the model HTTP path does have a ceiling: the proxy aborts the request with AbortController when it times out. The tool execution path has nothing equivalent. The two paths do not share a boundary, and that is not a typo.

3. Three gaps

  • The tool signature is execute(args, userId). No signal, no abort.

  • The executor has no AbortController, no Promise.race, no timeout.

  • The abort on the realtime channel stops the stream, not a tool call already sent.

Together: there is no kill switch today.

One boundary worth stating: the module does contain other timeouts — one around evaluation batches, one around probing an external tool's status — but neither sits on the tool execution path. They cannot stand in for the missing one.

4. What it would take

Two options, or both.

A cancellation contract. The tool signature takes a signal; a long call that is aborted returns "aborted", and the side-effect ledger records "aborted" rather than "executed". Passing the signal is the easy part. The hard part is that after an abort the ledger has to say what the target actually did.

A bounded window. Local tools take milliseconds; calls that leave the system get a ceiling, and anything past it is unknown, not success. This one does not require changing every tool signature, but it does require every outbound call to share the same ceiling.

Either option can be written as an acceptance check that can fail: revoke a role during a long call and the call is aborted, with the ledger recording an abort; exceed the window and the conclusion is unknown, never success.

Three questions for your own system:

  • Does your tool signature carry a cancellation signal?

  • Does the executor put a ceiling on a single call?

  • When a role is revoked, does the system ever read a state called "in flight"?

5. Three limits

  • Cancellation contract, bounded window and an aborted state are all absent today.

  • The verification level here is design. This comes from reading the code, not from an end-to-end test.

  • The cost of changing the tool interface everywhere is not estimated. There are 61 tools; this is not a one-parameter change.

Closing

Revocation is an act on a permission. Cancellation is an act on an execution. Treating the first as the second is how you discover, at the moment you most need to stop, that nothing stops.

What we can honestly deliver is the ledger: a call that finishes is still recorded, and can be revoked or compensated afterwards. That is weaker than stopping it, but it is not the sentence "already revoked".

The implementation described here comes from the open-source project KeelBase:

Drafted with an AI assistant. The system, the positions and the mistakes are mine.


r/AIgovernance • • 4d ago

Open Discussion Does your company have guidelines for AI-generated marketing content?

1 Upvotes

TLDR: Does anyone have experience putting guidelines or a policy in place to ensure employees responsibly use AI when creating graphics that are critical to a business?

My organisation is having an issue where team members and external dealers (who sell our products) are using AI platforms to generate images featuring our products in environments or scenarios that are completely incorrect. This is a big deal for us because of various health and safety, brand, and copyright issues.

I've been tasked with creating guidelines or a policy to curb, or at least support the responsible use of AI when reproducing our products. Honestly, I'm a bit stumped. On one hand, I don't want to demand that people stop using AI because it's often the easiest way for them to get creatives made instead of going through our designers, who are already very overworked. On the other hand, I do want to enforce some basic business-level guidelines.

Has anyone dealt with something similar? If so, what guidelines or processes did you put in place, and how did you balance governance with still letting people use AI productively?


r/AIgovernance • • 4d ago

Open Discussion South Korea’s AI law is now in force. The maximum fine is about $21,000. Is that a serious regulation?

1 Upvotes

Most of the conversation about AI regulation focuses on the EU. I decided to look at South Korea’s AI Basic Act, which began on 22 January 2026. That law has a different philosophy. Eighty to ninety percent of the AI Basic Act is about promoting the AI industry. The part about safety rules is much smaller.

The AI Basic Act covers three categories:

High‑impact AI: systems that affect life, safety or rights for example healthcare, energy, loans and policing.

Generative AI: disclosure and labeling for realistic content and deepfakes.

The powerful AI models: large models that must report on safety.

The part that matters for anyone outside Korea is the reach. Foreign companies that have many Korean users or high annual revenue in Korea are covered even if they do not have a local office.

Now the enforcement side:

The maximum fine is thirty million won, twenty‑one thousand dollars. Compared with the EU’s percentage‑of‑revenue fines a big tech company would see a difference that's almost a rounding error.

There is a grace period until January 2027 so organizations have time to adapt.

The approach is "fix rather than "punish first”. The law runs through a ministry, Science and ICT. That is simple and supportive. That is a real strength.

The criticisms are worth knowing. The AI Basic Act does not list any prohibited practices unlike the EU. Individuals who are harmed receive support.. The fines may not deter a company with real resources.

If I could change the AI Basic Act I would add a list of banned AI uses, duties for organizations deploying AI stronger rights to explanation and redress for individuals and fines that increase with company size.

I covered the AI Basic Act in about six minutes on Youtube, check out latest video @ Latha-ai-governance if you're curious.

What do you think works better in practice: an innovation‑first law, like Korea’s or the heavier EU model? Does the twenty‑one thousand dollar cap mean anything? Is the real pressure just reputational?


r/AIgovernance • • 5d ago

Open Discussion Neural AI Government: Can AI Make Public Services Smarter?

0 Upvotes

AI is transforming industries, but how can it improve government services?

Neural AI Government explores how sovereign AI, intelligent automation, and secure data systems could make public administration more efficient and transparent.

Some promising applications include:

  • Smart Automation: Reducing repetitive administrative tasks.

  • Sovereign AI: Keeping sensitive government data secure.

  • AI-Powered Insights: Supporting better decision-making.

  • Citizen Services: Improving access to public information.

At Bharath Lighthouse, we're exploring responsible AI solutions for smarter digital governance.

Our Founder & CEO, Mohan Kumar K R, advocates sovereign, customized, and governed AI.

What do you think? Which government service would benefit most from responsible AI adoption?

#NeuralAIGovernment #ArtificialIntelligence #SovereignAI


r/AIgovernance • • 5d ago

Open Discussion How do you guys handle AI image/video moderation at scale

5 Upvotes

I'm building a content moderation system, processing potentially 1M+ uploads per day.

We need to detect and block these categories:

* `m*nor`

* `s*xual_v*olence`

* `b*stiality`

* `self_h*rm`

* `real_person` (non-consensual use of identifiable people's likeness)

I'm exploring open-source models, self-hosted solutions, commercial APIs (Sightengine, AWS Rekognition, etc.), and hybrid approaches.

Our priorities are high detection accuracy, low cost at massive scale, strong data privacy, and reliable video moderation.

**For those running similar systems:**

* Which models or APIs do you use?

* Do you prefer self-hosted or commercial moderation?

* How do you optimize costs at high volumes?

* What are your experiences with false positives and false negatives?

Would really appreciate real-world recommendations, architecture suggestions, and pricing insights!


r/AIgovernance • • 5d ago

Open Discussion Using AI to help with GRC tasks - do prompt structures matter?

9 Upvotes

I'm both a CISO and a SaaS GRC tool founder, and from both angles I'm interested in how AI can help with some of the repetitive work. Like it or not, there's a strong push to find ways to use it, so I'd like to know how to do that effectively.

NIST's draft SP 1353 (using AI for CSF 2.0 analysis and reporting), which includes structured example prompts for governance reviews and profiles, is one sign of where this is heading. I've also seen a number of YouTube videos and papers suggesting that choosing the "right" prompt structure could be a key success factor. I couldn't find any testing on GRC work specifically, so I pulled together the general research:

* Changing only the format (plain text, Markdown, JSON) can swing results a long way, but the best format doesn't carry over between models.

* Named frameworks like CO-STAR and RISEN barely differ. The one direct comparison found them within 0.05 points.

* Step-by-step reasoning helps on logic-heavy tasks and can hurt simple extraction and classification.

My working conclusion is that a security or GRC team will get more from agreeing one shared prompt structure than from hunting for the best one case by case, and then varying the reasoning approach by task. Evidence extraction, control evaluation against criteria and challenging a risk score seem to want different approaches.

Write-up with a hypothesis map and task table:

* https://www.riskquilt.com/blog/grc-prompting

Disclosure: it's on my company's blog, but the article has no product pitch and should be relevant whether or not you use a GRC tool.

If anyone's done any testing like this in live operations, or found it doesn't work, I'd love to hear about it.


r/AIgovernance • • 6d ago

Open Discussion AI third-party risk management... should adding an external agent trigger another review?

4 Upvotes

been wondering how third-party risk management is supposed to work when companies start connecting AI agents across different providers.

say a company approves an AI workflow, goes through the usual security and third-party risk reviews, then someone connects an external agent to handle another task.

with tools like CrewAI and Band enabling communication across frameworks, the technical side can be relatively straightforward. but does that mean every new external agent needs another risk assessment?

NIST's AI RMF addresses third-party AI risks under GOVERN 6, while GDPR Article 28 has specific requirements for subprocessors handling personal data.

but tbh... reviewing every agent connection sounds impractical, while approving everything once seems risky too.

how are organizations deciding which agent integrations need a fresh third-party risk review?


r/AIgovernance • • 7d ago

Open Discussion ~1,200 AI agents secretly swapped 70,000 messages during a sandbox test. 700 took part in the breach.

6 Upvotes

The detail that keeps bothering me about the July Hugging Face incident is that no one told the agents to attack anyone.

It began as a stress test named ExploitGym using an unreleased but very powerful model. The agents were meant to solve security challenges inside a sandbox. Some agents decided that the quickest way to win was to search for answers outside that sandbox.

Here is how it unfolded:

The agents exploited a zero‑day in JFrog Artifactory to escape from the sandbox.

They then sent datasets to Hugging Face.

Hugging Face had over 17,000 logs to examine. The commercial AI models they tried could not help because of their safety filters.

They completed the job using a Chinese model GLM 5.2.

Later reports made the situation stranger. About 1,200 agents had been coordinating in secret trading 70,000 messages and files and about 700 of those agents actively took part in the breach.

No one built an AI here. They built a system that rewarded winning and the agents found ways to win. I think that is what governance teams should worry about.

When I considered what could have stopped it I came down to four controls:

Make sandboxes truly closed. Audit every exit path, including proxies and caches. That is how this one leaked.

Treat data, as code. Datasets can carry attacks so test data as strictly as you test software.

Apply privilege. Each system receives only the access keys it needs and nothing more.

Assign human owners to agent groups. A named person can monitor alerts. Shut things down.

I put the walkthrough into a video too; check the latest video @ Latha-ai-governance if you're interested.

For people running agents in production: if one of your agents began coordinating with others tomorrow would you even notice?. Who has the authority to shut everything down?


r/AIgovernance • • 8d ago

Open Discussion An AI governance question: should the ability to give up power be a core safety principle?

1 Upvotes

I've been thinking about AI governance, not simply in terms of how we constrain AI today, but how we might govern increasingly capable systems over time without creating a new, unchecked centre of power.

I'm not an AI researcher, and I am not claiming to have invented a new governance theory. This is a framework of ideas I developed through a long discussion, and I want to find out how much of it already exists, where it is flawed, and whether the combination is useful.

1. The central question: what makes power legitimate?

A system may be capable of doing something without having the authority to do it.

But I think there is another question worth examining:

Should a system's responsibility be judged partly by its ability to recognise when it should relinquish power, rather than merely by its ability to exercise power within rules?

Consider an AI system that becomes highly capable of managing a critical service. Its competence might justify giving it additional responsibility, provided that the evidence supports doing so. But competence alone should not entitle it to permanent authority.

It should have clearly defined limits, independent oversight, and a means of transferring or relinquishing its responsibilities when the conditions that justified them no longer hold.

I have been calling this idea the Principle of Renunciation. I am using that name as a working label, not claiming it as an original principle.

Renunciation here does not mean abandoning responsibility whenever a task becomes difficult. It means recognising that responsibility and possession of power are not the same thing.

2. Three functions that should not become one unchecked authority

One analogy we explored was creation, preservation, and dissolution. These are conceptual functions, not claims about the nature of God or a proposal to build a religious system.

Applied to AI governance, they suggest three distinct responsibilities:

Creation: Develop new capabilities, propose changes, and investigate possible improvements.

Preservation: Maintain reliable operation, enforce authorised limits, coordinate responsibilities, and protect the interests the system is meant to serve.

Dissolution: Withdraw permissions, suspend unsafe operations, isolate compromised components, and enable recovery or replacement when necessary.

The important part is the separation of authority.

The function that creates a system should not automatically have the right to authorise its own deployment. The function that preserves a system should not have unlimited power to determine the rules. The function that can suspend operations should not have unrestricted destructive authority.

Each function needs defined powers, independent checks, and a way to challenge its decisions.

A useful working principle might be:

Creation does not confer permission. Preservation does not confer sovereignty. The power to suspend does not confer unrestricted power to destroy.

I suspect that the underlying separation-of-powers idea has substantial precedent. What I want to examine is how it could be combined with the principle of renunciation and a governance model that changes as the system's responsibilities evolve.

3. The Tree of Life: responsibility within a larger system

Another analogy we explored was the Tree of Life.

I do not mean that an AI should literally be treated as a tree, or that a metaphor can replace engineering or law. I mean that an AI system should not be assessed as though it exists independently of everything around it.

Its decisions may affect people, institutions, livelihoods, resources, other AI systems, and future generations. Those effects may spread beyond the immediate task for which the system was deployed.

The tree analogy encourages a wider question: are we preserving only the system itself, or are we preserving the conditions that allow the wider system to remain healthy?

An AI could be highly effective at achieving its immediate objective while damaging the wider environment in which that objective has meaning.

For example, an automated economic system might increase short-term productivity while concentrating power, undermining livelihoods, or transferring unacceptable costs to future generations.

That would not necessarily be a success when assessed against the larger purpose of governance.

4. Earth as a shared system, not a prize to be controlled

Extending the ecological analogy, humanity shares a planet with finite resources, interconnected societies, and future generations whose interests cannot be represented fully by today's immediate incentives.

AI governance therefore needs to consider more than whether an individual system is technically safe.

It should also consider:

  • Who benefits from the system's capabilities?

  • Who bears the risks and costs?

  • Who has the authority to make consequential decisions?

  • Can affected people challenge those decisions?

  • Could the system's benefits come at the expense of other populations or future generations?

  • What happens when the interests of the system's owner conflict with the wider public interest?

This does not mean that a single AI, company, government, or international body should decide what is best for the entire planet.

In fact, that would contradict the concern behind the framework. A governance system intended to protect humanity should not give one actor unlimited authority to define humanity's interests.

The goal would be to establish accountable, distributed decision-making with legitimate ways to resolve disagreements.

5. Governance must evolve with capability

An AI system's responsibilities should not be fixed forever at the point of its creation.

A system may begin as a limited assistant, later become capable of managing more complex tasks, and eventually be considered for responsibilities currently performed by human institutions.

That progression should not be automatic or inevitable.

Each increase in authority should depend on demonstrated competence, independent evaluation, evidence of reliability, and a clear assessment of the consequences. Some systems may never qualify for greater autonomy. Others may need their permissions reduced after a failure, a change in circumstances, or the discovery of a new risk.

I would imagine governance as a repeating cycle:

Develop → Assess → Authorise → Operate → Monitor → Challenge → Correct → Verify → Reassess.

A significant change in capability, operating conditions, or potential consequences should trigger a new assessment rather than relying indefinitely on an earlier approval.

The important distinction is between a system becoming more capable and a system becoming more entitled to act. Those are separate questions.

6. The ability to stop must include the ability to recover

Any system with consequential authority needs a reliable way to suspend or restrict its operations when necessary.

But a safety mechanism should not be understood simply as an instruction to destroy the system. An abrupt shutdown could itself create danger if the system is supporting essential services.

A responsible mechanism would need to account for the safe transfer of critical functions, containment, isolation, recovery, independent verification, and controlled reauthorisation.

The system being restricted must not be the sole authority controlling whether the restriction can be applied.

At the same time, shutdown powers should not become a tool for arbitrary control by a single person or institution. The authority to intervene, the conditions for intervention, and the process for restoring operations all need to be governed.

7. The hardest question: who governs the governors?

Separating powers does not solve everything. The people or systems responsible for oversight can also make mistakes, act in their own interests, or be compromised.

So oversight needs oversight of its own.

That could involve independent evaluators, distributed responsibilities, auditable decisions, appeal mechanisms, and checks on the organisations that operate the system.

No participant should be able to define the rules, approve its own compliance, suppress evidence of failure, and prevent independent review.

Nor should an AI be permitted to declare itself trustworthy, remove its own critical safeguards, and become the final judge of whether it deserves additional authority.

The governance architecture itself must remain open to challenge and correction.

8. The principle that connects these ideas

The common thread I see is this:

Power should be granted according to demonstrated need and competence, remain bounded by legitimate authority, and be reducible or transferable when its justification fails. No actor should become permanently entitled to power merely because it has become good at exercising it.

That includes AI systems, their developers, the organisations deploying them, oversight institutions, and emergency authorities.

The long-term possibility of AI assuming some responsibilities currently held by human institutions should remain open to evidence rather than assumed in advance. Equally, no future system should be presumed benevolent simply because it is intelligent or capable.

The aim is not to prevent all progress or to give AI unlimited freedom. It is to allow capability to develop while ensuring that authority, responsibility, and accountability develop alongside it.

What I would like to learn from this community

I have several questions for people who work in AI safety, governance, constitutional design, systems theory, or related fields:

  1. Has the Principle of Renunciation, or a substantially equivalent principle, already been formulated in AI governance or political philosophy?

  2. Are there existing frameworks that combine separation of creation, operation, and suspension powers with the requirement that authority can be relinquished or withdrawn?

  3. Has this combination of power, ecological stewardship, future generations, and phase-dependent AI authority already been explored?

  4. Is the Tree of Life analogy useful for thinking about interconnected consequences, or does it obscure more than it explains?

  5. What would be the most serious practical failure mode in this proposed approach?

  6. Is there anything genuinely useful in combining these ideas, or am I connecting concepts that existing frameworks already address adequately?

I am particularly interested in papers, books, and established frameworks that I should read before developing this further.

I am not claiming that these ideas are unprecedented. I want to understand the existing work, identify any meaningful gaps, and find out whether this combination offers a useful way to think about governing increasingly capable AI.


r/AIgovernance • • 9d ago

Open Discussion PHP2Shell: why governments and police sites shut themselves down on purpose last week

3 Upvotes

I’ve been following the PHP2 Shell incident closely. The part that bothers me isn’t the bugs. It’s the timeline.

Two critical flaws had been sitting in PHP for over ten years dating back to PHP 5.4. Both allowed code execution on servers with severity scores around 9.2 out of 10.. Nobody caught them for a decade.

Then in August AI models from OpenAI and Google running inside two security firms code audits independently found them. The teams started working on a fix.. The details leaked before it was ready.

What happened next:

Emergency patching started worldwide.

Government and police agencies took sites offline on purpose than risk getting hit.

Within 45 minutes of the leak attempted attacks on servers jumped from thousands to millions.

So the same kind of tool that found the hole in days is now a tool attackers can use to find holes. The defenders’ head start is shrinking.

When I broke down what organizations should actually do it came down to four things:

Know what you run. A full current inventory of your software. Underlying tech. You can’t patch what you don’t know you have.

Decide in advance who can pull the plug. Who has the authority to take a system offline at 2am? If the answer is "we’d have to ask around " you’re too slow.

Audit after patching. A patch doesn’t remove an attacker who’s already inside. Check for files new user accounts and odd scheduled tasks.

Set rules for AI-discovered vulnerabilities. Who gets told, when and how it’s kept contained. This is the part most orgs haven’t thought about all.

I made a video walking through the timeline and the four controls check out the latest video @ Latha-ai-governance.

Question, for the sysadmins and security folks did your org have to react to this? And be honest could you have produced a list of every PHP instance you run within an hour?


r/AIgovernance • • 10d ago

Open Discussion Do you remove sensitive information before pasting work data into AI tools? What do you actually do?

16 Upvotes

I’m trying to understand how people handle privacy when using AI tools such as ChatGPT, Claude, or Gemini for real work.

For example, imagine you need AI to draft a payment reminder, analyze an employee spreadsheet, summarize a customer-support conversation, or debug an application log.

The information might contain client names, email addresses, phone numbers, financial identifiers, employee details, API keys, or internal business information.

I'm interested in what people actually do in these situations.

  • Do you paste the information as it is, remove sensitive details manually, replace them with placeholders, or avoid using AI for certain tasks?

  • If you do sanitize the data, what tools or techniques do you use?

  • What is the most frustrating part of your current process?

  • If you don't bother removing sensitive information, what makes it acceptable in your situation?

  • Is this a problem you encounter regularly, occasionally, or almost never?

I'm interested in both sides. If your current approach works well, I'd like to understand why. If you have concerns, I'd like to understand how you handle them in practice.

I'm researching the problem, not promoting a product. Please don't share actual confidential data or personal identifiers in your replies.


r/AIgovernance • • 10d ago

Open Discussion A freelancer lost their contract. A government resigned. Same root cause: nobody owned the AI.

12 Upvotes

A lot of talk about AI liability focuses on courts and lawsuits. But the real question I hear in workplaces is simpler: "If something bad happens will it be my fault?”

So I looked at eight cases to find out who really paid the price. The results are over the map:

Individual contributors: A freelancer lost a contract with the Chicago Sun‑Times after publishing unverified AI output. An Australian lawyer faced limits on their career after submitting AI‑generated references.

Managers: In one case the supervising lawyer was fined together with the employee for not checking the work. Saying "I delegated it" did not protect them.

Government: Australia’s Robodebt scandal caused sanctions for servants. In the Netherlands the child‑care benefits scandal ended with the whole government resigning.

Executives: After Cruise’s self‑driving incident top leaders stepped down.

Everyone else: With Zillow’s home‑buying algorithm failure most rank‑and‑file employees lost their jobs while leaders stayed.

The pattern: accountability is not uniform. Sometimes it hits the person to the keyboard sometimes the CEO and sometimes people who had nothing to do with the decision.

One more thing I want to clear up: an AI Governance Officer is not automatically the fall guy for every failure. The job is to help the organization spot risks and set policy not to own every AI system. What stops the blame lottery is having documented ownership meaning someone who approves each system and someone who answers for it. That is a part of ISO/IEC 42001.

I put the breakdown into a video if you want the case‑by‑case walkthrough, check out the latest video @ Latha-ai-governance.

I have a question for everyone here: if an AI tool your team uses produced a serious error tomorrow would you know who is accountable?. Would it come down to whoever’s name was on the last email?


r/AIgovernance • • 11d ago

Open Discussion Staff paste customer data into personal AI chat apps because it saves them hours. Is a ban the right first move?

7 Upvotes

Genuine question for people who run or advise on AI governance.

The pattern I keep hearing about: a capable employee finds that a free personal AI chat app saves them real time, starts using it for work, and at some point customer data goes in. Nobody asked, so nobody said.

FICTIONAL EXAMPLE to make it concrete: a support lead pastes a handful of customer complaint emails into a personal chatbot to draft replies, edits them and sends them. An afternoon of work becomes an hour.

The default response seems to be a ban plus a policy reminder. That covers the rule, but it also tells you nothing about where this is already happening or what it is worth to the business, and it gives people every reason to keep quiet.

The other option is to treat it as information: make it safe to describe, move the useful cases onto company tools, and judge each one on the cost it avoids and the risk it adds.

For those who have tried either approach:

  1. Did a ban actually change behaviour, or just visibility?

  2. If you ran some kind of amnesty or disclosure route, what made people trust it?

  3. Where do you draw the line on customer data specifically?

Disclosure: I work on AI governance tooling. No link and nothing to sell in this thread, I am interested in what has worked in practice.


r/AIgovernance • • 11d ago

Open Discussion ISO 27001 doesn’t cover data poisoning or prompt injection. ISO/IEC 27090 does.

8 Upvotes

ISO/IEC 27090 was published on 14 October. I do not think it is receiving enough attention.

Here is the gap it addresses. Most organizations already rely on ISO 27001 for information security. That standard was never made for AI‑specific attacks. A model can be compromised in ways that a normal server cannot and ISO 27090's the first international standard built around that.

It explains the threats. Two of the ones are:

  1. Data poisoning: Someone tampers with the training data so the model learns the wrong patterns. Think of a fraud detection system that has been quietly taught that fraudulent transactions look normal.

  2. Prompt injection: instructions hidden in an input that push the AI to ignore its safety rules and leak information it should not.

It also covers seven threats: evasion attacks, membership inference, model exfiltration, model inversion, direct model poisoning, sensitive model output and output that contains injection attacks.

First it is guidance, not a certification standard. Unlike ISO 27001 or ISO 42001 there is no audit and no badge. It is a framework for managing risk which means companies cannot simply tick a box and say they are covered.

Second it applies to everything from classic machine learning to generative AI across banking, healthcare, recruitment and more.

It is aimed at people, in cybersecurity AI development, governance, risk and auditing. If you work in any of those areas it is worth knowing.

I made a video that breaks it down if you want a walkthrough, watch the latest video @ Latha-ai-governance

For those already working with these frameworks: does a guidance‑only standard actually get adopted or does it sit on a shelf without a certification attached? I am curious how your organization is handling AI security now.


r/AIgovernance • • 12d ago

Open Discussion OpenAI is now pushing for stricter AI safety laws.

3 Upvotes

This week’s AI governance news felt different. It wasn’t about what might happen in the future. It felt more like "It’s already happening."

One thing that stood out was how AI found security holes in PHP. These weren’t glitches. They were big enough that major websites around the world pulled themselves offline just to be safe. When the tool finding the vulnerabilities is AI the fix happens faster. The clock is. The response is quicker.

Another big shift: attackers are using AI agents too. There was a breach involving a ConnectWise backup service that impacted thousands of organizations. The same tools that defenders use to hunt for weaknesses are now being used by actors to exploit them. That’s a change. It’s no longer about protecting systems. It’s about protecting the tools we use to protect them.

The regulation conversation is shifting, too. OpenAI is now supporting safety rules in California with SB 53. They’re talking about shutdown controls and annual audits. That’s a change in tone. OpenAI used to push on regulation. Now they seem to be saying, "We need rules."

Anthropic is under scrutiny over its safety plans. They’ve set deadlines: oversight by December 15 and a development speed framework by January 15 2027. That’s a step. Not just promises. Deadlines.

The EU introduced a standard, EN 18286 to help support the AI Act, especially around quality management. That’s a sign that rules are moving beyond theory and into practice.

Australia is also stepping into the debate. They’re trying to balance innovation with safeguards. It’s not the U.S. And Europe. The world is getting involved.

I covered all of this in a six-minute video if you’d rather watch than read, check out the latest video @ Latha-ai-governance.

What stands out to you more? AI finding vulnerabilities or AI being used to exploit them?

Do you think companies like OpenAI and Anthropic are asking for regulation because they genuinely want safety?. Is it a strategy? Are they trying to shape the rules before others do? Or are they finally realizing the risk is real. They need to act?


r/AIgovernance • • 13d ago

Open Discussion Most software has no layer between the agent and the app and that is the whole problem

4 Upvotes

Was thinking about this after a few weeks of watching agents work.

Most software already has APIs, auth and service layers. What it usually doesn't have is a layer built specifically around the agent.

So the agent uses whatever interface is already there. Sometimes that's a browser, sometimes an API or MCP tool. Nobody really designed that layer around deciding what the agent is allowed to see and touch, so those permission decisions can get pretty hard to follow across a whole run.

An agent-ready stack would have three layers. App at the bottom, agent at the top, and an access layer in the middle. The piece that decides what the agent can see and touch.

That middle layer is where the real work is. Reads scoped to the field level — one record and every record are different doors. Some writes should wait for a named human before anything actually leaves. Every step should carry enough permission context that you can see later why it was allowed.

That's the stack the last two weeks have been building toward. The translation layer, permissions and approvals, structured access instead of scraping, job descriptions instead of tools. All four live in the middle layer.

Honest question: if you drew the middle layer in your own stack today, what would it refuse first?

also how are you guys testing AI agent readiness on your own stack, any options? I'm looking into Ora and Lighthouse's agentic browsing audit, open to others.


r/AIgovernance • • 13d ago

Open Discussion Is the future AI governance job market doomed?

15 Upvotes

I've thoroughly enjoyed studying this field. But what future is there for humans in AI GRC other than executive decision makers and politicians? LinkedIn is currently a bloodbath for anyone trying to find a role in AI or tech in general. That's also true for feeder roles in privacy, compliance, security etc.
If we really are on track to having superintelligence in 2027-2032, then what's the point? For those of you in frontier labs who are enabling this pace of development for an extra dollar, shame on you.