AI Agents Are Already Working for You. Who’s Managing Them?

AI Agents Are Not Applications. They Are Digital Workers.

Most organizations are adopting AI agents faster than they are learning how to govern them.

That is the problem.

A chatbot that answers questions is one thing. An AI agent that can access business data, use tools, trigger workflows, generate artifacts, make recommendations, or alter enterprise state is something else entirely.

At that point, the organization is no longer just deploying software.

It is introducing a new kind of operational actor.

That actor needs identity.

It needs boundaries.

It needs oversight.

It needs evidence.

It needs a human owner.

It needs a kill switch.

In other words, AI agents must be managed more like digital workers than ordinary applications.

AIAgentBanner

The Governance Gap Is Already Here

Across enterprises, mid-market firms, and small businesses, the same pattern is emerging:

  • Business teams are experimenting with agent workflows.
  • Security teams are trying to understand the new control surface.
  • Legal and HR teams are still catching up.
  • Executives want productivity gains without slowing the business down.
  • Audit, compliance, and risk teams are asking for evidence that often does not exist.

The dangerous assumption is that existing software governance, SaaS controls, service accounts, and general “responsible AI” policies will be enough.

They usually will not be.

AI agents create new questions:

  • Who or what is this agent in the enterprise?
  • What systems can it touch?
  • What decisions can it influence?
  • What actions can it take without human approval?
  • What evidence exists if something goes wrong?
  • Who owns the agent’s behavior?
  • How do we suspend, investigate, or retire it?

If leadership cannot answer those questions, the organization does not yet govern its agents.

Why Traditional Software Governance Falls Short

Traditional software governance usually assumes that applications behave within relatively stable boundaries.

Someone writes the code.

Someone approves the deployment.

Someone grants access.

The system then performs the tasks it was designed to perform.

AI agents are different.

They interpret instructions. They infer next steps. They retrieve context. They call tools. They may chain actions together. They can create outputs that look polished and authoritative even when they are incomplete, wrong, or unsafe.

That changes the risk model.

The critical question is no longer simply:

“Can the system perform the task?”

The better question is:

“What happens when the agent performs the task incorrectly, partially, opaquely, or adversarially?”

That is where governance has to catch up.

The Six Planes of Agent Control

In the full e-book, I introduce a practical model called the six planes of agent control:

  1. Identity — Who is this agent in the enterprise?
  2. Policy — What is it allowed to do?
  3. Tool — What can it touch?
  4. Runtime — Where and how does it execute?
  5. Observability — What evidence exists about its behavior?
  6. Governance — Who approved it, owns it, reviews it, and can stop it?

This model gives executives, CISOs, boards, engineering teams, HR, legal, and GRC functions a shared language for managing agentic AI before uncontrolled adoption creates avoidable risk.

It also forces a hard but necessary shift:

Stop governing only the application.

Start governing the actor-like behavior.

Why This Matters Now

The answer is not to reject AI.

That would be strategically weak.

The answer is also not to let every department wire agents into business workflows with broad access, vague accountability, weak logging, and no structured review.

That would be reckless.

The rational path is selective adoption with governance first.

Organizations that get this right will be able to move faster because they can prove where agents exist, what authority they have, what controls apply, and how failures will be contained.

Organizations that get it wrong will eventually face the predictable consequences:

  • unclear accountability
  • invisible privilege paths
  • poor evidence
  • data exposure
  • automation bias
  • workflow drift
  • legal ambiguity
  • emergency cleanup after controls should have been designed in from the beginning

This is not a theoretical problem. It is already showing up in real adoption patterns.

Download the Full E-Book

I have released a new e-book:

AI Agents Management Framework: Policy, Procedure, and Governance Controls for Managing AI Agents as Digital Workers

Inside, you will find:

  • A governance-first model for selective AI adoption
  • The six planes of agent control
  • Identity, access, evidence, and oversight patterns
  • Practical guidance for executives, CISOs, boards, HR, legal, engineering, and GRC teams
  • Case narratives showing what we are seeing across large enterprises, mid-market firms, and small businesses
  • Sample policies, procedures, risk tiering worksheets, Agent System Record templates, autonomy budget examples, incident response addenda, and offboarding guidance

The central idea is simple:

If you govern agents like applications, you are governing the wrong thing.

To download the full e-book, register here:

https://signup.microsolved.com/ai-management-e-book/

What You’ll Get When You Register

  1. A practical AI-agent governance blueprint
    Download the full AI Agents Management Framework e-book and learn how to treat AI agents as managed digital workers, not ordinary applications. The framework helps leaders define ownership, authority, access, oversight, evidence, and shutdown procedures before agent workflows create unmanaged risk.
  2. Actionable controls you can adapt immediately
    The e-book includes practical models for identity, policy, tool access, runtime controls, observability, governance, risk tiering, autonomy budgets, Agent System Records, performance reviews, incident response, and agent offboarding.
  3. Executive-ready guidance for safer AI adoption
    Use the framework to help boards, executives, CISOs, HR, legal, engineering, and GRC teams align around a clear operating model for selective AI adoption, stronger accountability, and verifiable control.

About MicroSolved

MicroSolved, Inc. helps organizations improve security, governance, resilience, and operational trust in complex technology environments.

This e-book extends that work into AI-agent governance, with a focus on practical controls for identity, access, oversight, auditing, and enterprise operating model design.

New TISAX Guide Now Available

Unlock the power of strategic compliance with The Common Sense Guide to TISAX Compliance—a practical, no-nonsense roadmap designed for automotive industry players who need to get smart about information security, fast. Created by MicroSolved, Inc., this guide strips away the jargon and delivers real-world advice for mastering TISAX—from initial gap analysis to audit preparation and continuous improvement.

TISAXCompliance

Whether you’re a Tier 1 supplier, OEM partner, or part of the global automotive supply chain, this guide empowers your organization to:

  • Demystify the TISAX Framework: Understand how TISAX aligns with ISO 27001 and why it’s a must-have for automotive data protection.

  • Get Audit-Ready with Confidence: Use checklists, maturity models, and structured steps to eliminate surprises and build trust with partners.

  • Navigate Regional Threats & Regulatory Overlap: Tailor your strategy to address local cybersecurity threats while aligning with global standards.

  • Save Time & Resources: Learn how to avoid audit fatigue, reduce redundant efforts, and make smarter investments in compliance.

  • Gain Competitive Edge: TISAX isn’t just about passing an audit—it’s your passport to more contracts, deeper trust, and long-term growth.

Backed by decades of security experience, MicroSolved’s guide is your fast-track to understanding, implementing, and thriving under TISAX—no fluff, no filler, just actionable insight.

Get ready to turn compliance from a checkbox into a business advantage.

Click here to register and get a free copy of the ebook. 

Third-Party Authentication Inventory Worksheet

We often get asked for worksheet questionnaires to help organizations inventory their third-party applications and the underlying authentication mechanisms. 

As such, we have developed a template for our clients and others to use for this purpose. 

You can easily distribute this worksheet to each part of the business or group, empowering them to complete it for each of their third-party applications. 

Once they return the data, you can extract it into any aggregation tool or vendor monitoring system you use. If you don’t have those tools available, you can process and monitor them manually using this easy spreadsheet for each line of business. 

You can get the template spreadsheet here

As always, we hope these tools are helpful. Let us know if you have any questions or feedback. 

Intruder Pro Game Launched in GPT Store

Thanks to the launch of the OpenAI GPT Store, I am proud to announce the immediate availability of a new penetration testing game and hack-the-box simulation platform – Intruder Pro

Though not a product of MicroSolved, it is personally designed by our CEO and Security Evangelist, L. Brent Huston. 

The GPT is a text-based role-playing game that simulates real-world penetration tests and hack-the-box games. It leverages real-world tools, and teaches you a bit along the way. 

Even better, you can get a new simulation with new targets and new services to exploit every single game! The system can also provide coaching and score your efforts at any time in the game.

Feedback has been great, and people all around the world are playing, learning, and gaining insights about information security all at the same time. 

Check it out by clicking here and let me know on Twitter (@lbhuston) what you think! 

Video: Auditing Authentication Mechanisms

Here’s a quick video walkthrough of the presentation around auditing authentication mechanisms. 

We are getting some great feedback on this one, and people are rising to the challenge of doing audits for their organizations. Many folks are finding some quite unexpected results! 

Let me know on Twitter (@lbhuston) what you discover! 

 

As always, thanks for reading and watching! 

Why Emulate a PLC with a Raspberry Pi

One of the most powerful uses of emulating a PLC (Programmable Logic Controller) field device with a Raspberry Pi is that it provides an affordable and easily obtained platform for prototyping, performing ladder logic testing, and researching various industrial control systems and cybersecurity concepts.

Raspberry Pis are Affordable

Raspberry Pi models 3 and 4 are significantly more affordable than real PLCs. A typical PLC can cost hundreds or thousands of dollars.

The Raspberry Pi costs around $35-50 depending on your model choice. This makes them very accessible to hobbyists, students, researchers, developers, and anyone else who wants to work with the basics of industrial control systems. The low cost makes them ideal candidates to emulate a PLC in many scenarios.

Raspberry Pis are Easily Obtainable

PLCs can be quite difficult to come by, especially if you want one without any pre-existing software installed. Many manufacturers will not sell their products to third parties unless they have some kind of existing relationship. If you don’t already know someone at the manufacturer then you may need to pay a hefty upcharge. Additionally, purchasing the addons for power supplies, specific programming software, and such can quickly turn into a slog of paperwork and supporting tasks. The lead time and delivery times can take weeks to months.

The Raspberry Pi, on the other hand, can be purchased at many big-box electronics or computer stores, directly from many providers, or even delivered to your door from Amazon and other online sources. It uses a common USB power supply and can be configured and programmed using open source tools available online. Lead time is a couple of days to a few hours, letting you stay focused on your work.

The OpenPLC Project

The OpenPLC Project is a stable, well-documented toolkit for emulating basic PLC operations on the Pi. It has been used successfully to simulate a variety of different types of PLCs and includes support for ladder logic and other common PLC functions. You can find the programming reference and review the available capabilities here.

You can get OpenPLC up and running on a Pi in less than 30 minutes. In our testing, we were able to begin using the emulated PLC in our lab within an hour!

Going The Extra Mile With SCADABR

SCADABR is an open-source supervisory control and data acquisition software package designed to allow you to create interactive screens or human-machine interfaces (HMI) for your automation projects. It provides tools for creating graphical user interface widgets, event handlers, timers, and dialogs. With its ability to communicate with multiple controllers (including OpenPLC), ScadaBR is an ideal companion for the OpenPLC Runtime and Editor.

Using a Pi, OpenPLC, and SCADABR together, can get you a very powerful and useful PLC platform up and running for under $100 and in less than a few hours. Once implemented, you can use the platform to learn about industrial controls systems, ladder logic, PLC programming, and operations. You can also do basic ladder logic research and testing, and even prototyping for future real-world PLC deployments. Cybersecurity folks also have a very capable platform for learning about industrial control security requirements, performing vulnerability research, reverse engineering, or practicing their assessment skills in a safe environment.

While you might not get the full power of a true PLC (there are some limitations to Pi’s capabilities), you will likely get more than you expect. If you have an interest in or a need for some basic industrial control systems capabilities, this is a great place to start.

 

 

Automating SSL Certificate Management with Certbot and Let’s Encrypt

As we posted previously, following best practices for SSL certificate management is critical to properly secure your site. In that post, we discussed automating certificate management as a best practice. This post is an example of how to do just that.
 
To do so, we will use the highly-trusted free certificate provider Let’s Encrypt. We will also leverage the free certificate automation tool Certbot.
 

Installing Certbot

Installing Certbot is pretty easy, overall, but you do need to be comfortable with the command line and generally know how to configure your chosen web server. That said, if you check out the Certbot site, you will find a dropdown menu that will let you pick your chosen web server and operating system. Once you make your selections, simply follow the on-screen step-by-step instructions. In our testing, we found them to be complete and intuitive.
 

That’s It!

Following the on-screen instructions will have:

  • Certbot installed
  • Configure your web server for the certificate
  • Generate, get and install the certificate
  • Implement automatic renewals of the certificate to prevent expiration

You can literally go from a basic website to fully implemented and automated SSL in a matter of moments. Plenty of support is available from EFF for Certbot, or via Let’s Encrypt. In our testing, we ran into no issues and the implementation completed successfully each time.

Give it a shot! This might be one of the easiest and most effective security controls to automate. Together, Certbot and Let’s Encrypt can create a no-cost cryptography solution for your web sites in a very short amount of time.

Microsoft Making 2FA Easier with New App

Make sure you check this out if you use any of the Microsoft 2 factor authentication tools – they just released a new app for mobile devices to make their previously very painful mishmash of authentication tools easier!

I know a lot of clients and readers use the existing Microsoft authentication tools, so I will be eager to play with this and see just how much easier they have made it. Do you think it stands up to their claims of simplification? Let me know on Twitter (@lbhuston) what you come up with when you try it… 

80/20 Rule of Information Security

After my earlier this post about the SDIM project, several people on Twitter also asked me to do the same for the 80/20 Rule of Information Security project we completed several years ago. 

It is a list of key security projects, their regulatory mappings, maturity models and such. Great for building a program or checking yours against an easy to use baseline.

Thanks for reading, and here is where you can learn more about the 80/20 project. Click here.

Remember the Stolen Data Impact Model (SDIM)

Just a quick reminder about the work we did a few years ago on the Stolen Data Impact Model (SDIM) project. 

Many clients continue to use the project, the analysis sheet and the insights across their incidents. 

To learn more, here is quick and easy category search with the relevant links. Click here.

As always, thanks for reading and a huge thanks for supporting MSI!