# Managing Wild Code and AI-Driven Automation Risks Security teams must embed automated controls to govern rapidly proliferating employee-built AI workflows. - **Source:** [The Hacker News](https://brifing.si/source/f944ec2b-8180-47bc-94de-57085b5a6563) - **Published:** 2026-10-20 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/bf56c34b-10bc-46c1-89ca-e05e17153127 ## The Rise of Wild Code Employees are rapidly building AI-assisted workflows to automate daily tasks like lead routing and data summarization. This creates a phenomenon called wild code, where useful applications spread faster than established security processes. These builds often become critical operational dependencies before security teams even realize they exist within the corporate environment. ## Limitations of Traditional Governance Education, sandboxes, and steering committees are insufficient for managing modern AI code sprawl. While useful for setting policies, they fail to govern software that runs continuously after deployment. Committees often struggle to match the speed of employee innovation, focusing on engineering while overlooking shadow automations in finance or HR departments. ## The Runtime Security Problem Sandboxes effectively isolate prototypes but leave the runtime environment vulnerable once connected to live business systems. A successful test does not define appropriate production access or data permissions. Security teams must ensure that controls like monitoring and change reviews persist throughout the entire lifecycle of the application, not just during experimentation. ## Embedding Environmental Controls Sustainable security requires building controls directly into the environment where employees create and run their work. Instead of relying on manual oversight, teams should define permitted data sources and actions before systems connect. This approach ensures that security boundaries are applied consistently, preventing operational blind spots as new workflows go live. ## Defining Access and Permissions Permissions must strictly reflect the specific needs of a workflow rather than the broad access of its creator. Consequential actions should always require human approval to prevent unauthorized changes. Relying on prompts to restrict agent behavior is inadequate; security teams must enforce hard boundaries at the system and data access layer. ## Balancing Friction and Speed Governance should not create excessive friction, or employees will inevitably seek workarounds to maintain productivity. Security teams must provide accessible building experiences that meet business needs while keeping safeguards active. By automating routine requirements, security professionals can focus their limited time on reviewing high-risk access and sensitive, consequential business actions. ## Ensuring Traceability and Accountability Organizations must maintain clear records of ownership, execution identities, and change history for all automated workflows. This visibility allows security teams to pause processes or revoke access when behavior diverges from expectations. Human judgment remains essential for reviewing significant changes and responding to incidents, ensuring that accountability is maintained throughout the process. ## Strategic Security Integration The goal is to make security a core component of everyday building rather than a cleanup exercise after deployment. By defining shared boundaries with IT and system owners, security teams gain confidence in their environment. This framework enables employees to solve problems efficiently while maintaining the necessary oversight to prevent data breaches. ## Sources covering this story - https://thehackernews.com/2026/10/what-security-teams-can-do-to-tame-wild.html — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._