<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Enterprise Security · Angus Strom</title><link>https://angusstrom.com/tags/enterprise-security/</link><description>Notes on information security, written slowly. AI security, enterprise security and purple teaming.</description><language>en-AU</language><managingEditor>hello@angusstrom.com (Angus Strom)</managingEditor><lastBuildDate>Fri, 20 Nov 2026 20:51:06 +1100</lastBuildDate><atom:link href="https://angusstrom.com/tags/enterprise-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Enabling GTM at the Speed of Vibes</title><link>https://angusstrom.com/posts/gtm-at-the-speed-of-vibes/</link><pubDate>Fri, 20 Nov 2026 08:30:00 +1100</pubDate><author>hello@angusstrom.com (Angus Strom)</author><guid>https://angusstrom.com/posts/gtm-at-the-speed-of-vibes/</guid><description>&lt;p&gt;&lt;em&gt;AI turned sales teams into builders. Why the old paved paths don&amp;rsquo;t fit them, and what a fast, safe path for GTM should look like.&lt;/em&gt;&lt;/p&gt;&lt;p&gt;Go-to-market (henceforth GTM) has one blindingly obvious goal at any company, getting products, services, and deals to market as quickly as possible to match buyer demand. The exact definition can of course slightly differ company to company but at the end of the day they are one of the primary direct drivers of new revenue for a company, often a well-oiled GTM team moves extremely fast to leap on opportunities for business and further revenue growth with days or even hours being the decider between a deal closing or failing.&lt;/p&gt;
&lt;p&gt;These days, everyone is a builder. AI productivity and coding tools have taken the distance between “I have an idea” and “it’s live” and shrunk it to almost nothing, and nowhere is that felt more than in GTM teams, Account Exec teams, and Sales teams. Take for example someone in sales who over morning coffee has an idea for a demo brochure to show a potential customer the power of their platform&amp;rsquo;s new feature. They describe it to an AI tool, it builds the thing, a hosting platform puts it on the internet, and it’s being used before lunch. No ticket, no review, no procurement, and nobody in security has any idea it exists. For that team it’s a genuine edge: the rep who can stand up a custom app in an afternoon beats the one waiting three weeks for a queue to clear.&lt;/p&gt;
&lt;p&gt;That edge is real, and I’m not here to argue against it. But what does that same app look like six months later? Who owns it? What data is in it? Is it public? Whose card is paying for it? Momentum is going to beat slow security processes every time. So the job isn’t to slow GTM down. It’s to give them a safe path that’s faster than the one they found.&lt;/p&gt;
&lt;p&gt;Yes, we are once again discussing paved paths but with &amp;ldquo;AI&amp;rdquo; now.&lt;/p&gt;
&lt;h2 id="three-weeks-vs-three-minutes"&gt;Three weeks vs three minutes&lt;a class="anchor" href="#three-weeks-vs-three-minutes" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Paved paths aren’t a new idea by any means, but they’ve mostly been built by developers, for developers. They’re structured, often rigid routes to production that assume whoever is using them is technically savvy: comfortable with Git, pipelines, infrastructure as code and a command line. For years that assumption held. You wouldn’t expect a salesperson to build an interactive application. It was well outside their role. With AI, that’s no longer true. Again, everyone is a builder now.&lt;/p&gt;
&lt;p&gt;So now the paved path has non-technical people using it, or more often, not using it. Many GTM folks don’t even know it exists, because their whole view of how to build and ship is whatever their AI tool tells them. Ask Claude where to host a fresh-looking new app and it’ll happily suggest Vercel, Cloudflare or AWS. Why wouldn’t it? It has no idea out of the box that your company has an internal paved path, let alone how to use it. Nobody chose the wrong road. The tool picked it for them.&lt;/p&gt;
&lt;p&gt;And even when someone does know the path is there, the maths rarely works. The official route means a ticket, a review, an environment request and a wait. Call it three weeks if you’re lucky. Vibe hosting platforms (aka prompt-to-app platforms) that build the thing and put it on the internet in the same breath, take less time than a coffee break. The safe road is a ticket, a review and a three-week wait. The other one is three minutes and a closed deal.&lt;/p&gt;
&lt;p&gt;That said, most of this is not defiance. These people aren’t going rogue, they’re usually just doing their jobs with the tools in front of them. And to be fair, the old paved paths are often overkill for what GTM actually wants to host. Most of them lead to one place, the same environment your product runs in, usually inside your SOC 2 scope, where everything inherits change approvals, reviews, evidence collection and access requests. That’s right for the product your customers pay for. A demo built on sample data for a single meeting doesn’t need any of it. A sales proposal built on a customer’s own financial figures is different, it needs real controls, like access limited to the right people, the data handled the way you promised the customer and a clear expiry. But it still doesn’t belong in your audited production environment either. When every app gets the process built for the riskiest thing you run, people go around it.&lt;/p&gt;
&lt;h2 id="make-the-safe-path-the-fastest-path"&gt;Make the safe path the fastest path&lt;a class="anchor" href="#make-the-safe-path-the-fastest-path" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;At this point it is clear GTM teams need their own environments and processes, built around how they actually work. People who were never technical can now build real applications with AI. They should be able to bring them up safely, in minutes, straight from the AI tools they’re already using with the toolset supporting their day-to-day use cases. This is a case for enablement of one of the fastest areas of enterprises, allowing for these builders to increase their revenue potential.&lt;/p&gt;
&lt;p&gt;The core of this is an internal Developer Experience (DX) product: a paved path and utility built specifically for GTM, treated like a product rather than a policy. This product should meet builders in their AI tools, enabling them from the tool all the way to a live, controlled app without them ever needing to know what&amp;rsquo;s happening underneath.&lt;/p&gt;
&lt;p&gt;So what does a path like that actually need to be both fast and safe?&lt;/p&gt;
&lt;h2 id="what-fast-and-safe-needs"&gt;What fast and safe needs&lt;a class="anchor" href="#what-fast-and-safe-needs" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;There is no one-size-fits-all version of this, such enablement needs to be cut to fit each individual company. Designed around the culture of its GTM team, and the technical boundaries of its environment. What I offer in this post is a set of guiding principles I would hold any version of this paved path to.&lt;/p&gt;
&lt;figure class="fig"&gt;
&lt;label class="swap has-orig"&gt;
&lt;input type="checkbox" class="swap-toggle" aria-label="Show the original image"&gt;
&lt;span class="swap-media"&gt;
&lt;img class="dither" src="https://angusstrom.com/posts/gtm-at-the-speed-of-vibes/safe-path.dither.png" alt="Flow diagram: an AI tool publishes to the platform, a risk gate (LLM judge plus scanners) routes apps as low risk (auto-approved), higher risk (human review) or production-like (full process). Low and higher risk apps are shared with prospects via link plus code or a one-time code, then expire unless the owner renews. Monitoring watches every step." width="770" height="846" loading="lazy" decoding="async"&gt;
&lt;img class="orig" src="https://angusstrom.com/posts/gtm-at-the-speed-of-vibes/safe-path.orig.webp" alt="" aria-hidden="true" width="770" height="846" loading="lazy" decoding="async"&gt;
&lt;/span&gt;
&lt;span class="hint" aria-hidden="true"&gt;&lt;span class="h-hover"&gt;hover&lt;/span&gt;&lt;span class="h-tap"&gt;tap&lt;/span&gt;&lt;span class="h-back"&gt;back&lt;/span&gt;&lt;/span&gt;
&lt;/label&gt;
&lt;figcaption&gt;The safe path, end to end. &lt;span class="sc"&gt;Hover or tap to see the original.&lt;/span&gt;&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;strong&gt;1. Minutes, not tickets (Speed)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Minutes from idea to live link for the common case. Auto-approval for everyday applications; humans only where risk calls for it, use LLM judges or known risky criteria to determine risk.&lt;/li&gt;
&lt;li&gt;Self-service as much as possible, with clearly defined process, pathways, and SLAs for anything not self-service. Nobody is left waiting in a queue wondering what happens next.&lt;/li&gt;
&lt;li&gt;The AI tools people already use know the path: connectors to publish, org-wide skills, company-wide instructions. The pathway must be built into the AI tool.&lt;/li&gt;
&lt;li&gt;Git and pipelines stay underneath, driven by the DX product, not shown to the end user. Operates in the background away from non-technical eyes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;2. Safe by default, reviewed by risk (Safety)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Sample data and safe templates by default; no production credentials locally. The platform holds secrets; builders and AI tools never see raw keys.&lt;/li&gt;
&lt;li&gt;Build authentication and authorization patterns into the platform, it isn&amp;rsquo;t a choice, it&amp;rsquo;s a given.&lt;/li&gt;
&lt;li&gt;Use LLM judges, tuned to spot your own company&amp;rsquo;s sensitive data, work alongside &amp;ldquo;old-school&amp;rdquo; signals like source code scanners and secrets scanning to decide each app&amp;rsquo;s risk profile.&lt;/li&gt;
&lt;li&gt;Low-risk apps auto-approved. Higher-risk apps go to a human, quickly.&lt;/li&gt;
&lt;li&gt;Anything production-like, such as an app touching core systems or live customer data at scale, leaves this path and goes through the full production process.&lt;/li&gt;
&lt;li&gt;Private by default, nothing goes public until it&amp;rsquo;s shared on purpose.&lt;/li&gt;
&lt;li&gt;Build the processes and platform to your company&amp;rsquo;s risk appetite, and needs for enablement. Let an informed leadership set the risk appetite.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;3. Easy to share, hard to leak (Sharing)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Sharing takes one step from wherever the app was built. Build the platform to provide public links with access codes with an inbuilt communication channel for sharing access codes.&lt;/li&gt;
&lt;li&gt;For higher-risk apps, like for customer-financial proposals, step it up: instead of a fixed code, the prospect gets a fresh one-time code sent to their verified email at the moment they request access, valid for a few minutes.&lt;/li&gt;
&lt;li&gt;Nothing for the prospect to sign up to. A short code, easy to enter on a phone in the middle of a meeting.&lt;/li&gt;
&lt;li&gt;One link and code per prospect, each with its own expiry, and the rep can revoke any of them instantly if a deal goes cold or a link ends up somewhere it shouldn&amp;rsquo;t.&lt;/li&gt;
&lt;li&gt;The rep can see when it&amp;rsquo;s been opened.&lt;/li&gt;
&lt;li&gt;Shared from a company-branded address, so it looks like it came from the company.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;4. Nothing lives forever, nothing is orphaned (Lifecycle)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Nobody asks the AI to take an app down, so the platform does it for them.&lt;/li&gt;
&lt;li&gt;Every app has a named owner and an expiry date from the day it goes live. 30 days at most in my view, easy to extend if more is needed.&lt;/li&gt;
&lt;li&gt;Renewing means the owner confirms they still need it, so ownership stays real rather than rubber-stamped.&lt;/li&gt;
&lt;li&gt;A reminder goes out well before expiry, so nothing disappears mid-deal.&lt;/li&gt;
&lt;li&gt;When someone leaves or changes role, their apps move to their manager or the account owner, never to nobody.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;5. One place to see everything, and to kill it (Visibility)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;One platform view of every app: who owns it, its risk tier, who it&amp;rsquo;s shared with, when it expires and what&amp;rsquo;s changed.&lt;/li&gt;
&lt;li&gt;Alerts when the risk shifts, like customer data turning up in a sample-data demo, or an owner leaving the company.&lt;/li&gt;
&lt;li&gt;One-click takedown and link revocation for when something does go wrong.&lt;/li&gt;
&lt;li&gt;A centralised command centre to control usage of the platform.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Getting these items right results in the sanctioned path not feeling like a security control to the majority of users. It just becomes the easiest way to get a demo or proposal in front of a customer.&lt;/p&gt;
&lt;h2 id="for-the-ones-who-still-go-around"&gt;For the ones who still go around&lt;a class="anchor" href="#for-the-ones-who-still-go-around" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Even with all of this, there will always be a few who decide their path is the right one, and for them the answer is monitoring and enforcement. Picture someone who used Vibe-App-Platform.com at their last job and, out of habit, keeps using it at their new one, even though it isn’t approved. One of the simplest signals you can have for this is your DNS logs. Watch for activity on the known vibe-hosting platforms, add an AI tool to classify the newly seen sites on those platforms, and you have a strong, cheap signal for whether they’re being used to host company data. This won’t catch everything, custom domains and personal devices will slip past, but it doesn’t need to. It just needs to give you a good picture of where the problem is, and there are many other potential signals to build this picture off.&lt;/p&gt;
&lt;p&gt;Once these signals are gathered, problem spaces can easily be identified. Enforcement doesn&amp;rsquo;t need to start heavy-handed; first contact can be as simple as a direct message informing the team that an approved paved path exists and to move their app across, often many teams early on won&amp;rsquo;t even know it exists. Perhaps the team has particular needs this Vibe-App-Platform.com platform gives them, interviewing them can be a great way to gather feedback to fit their needs and migrate them across. It&amp;rsquo;s when it becomes repeat cases that escalation to full enforcement may be needed, blocking the platforms, taking apps down, and bringing in people leaders. That being said, it is rarely wise to pull an app mid-deal unless in extreme circumstances, else it provides these teams ammunition to paint security in a bad light.&lt;/p&gt;
&lt;h2 id="momentum-wins-so-give-it-a-road"&gt;Momentum wins, so give it a road&lt;a class="anchor" href="#momentum-wins-so-give-it-a-road" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;GTM is going to keep moving fast, it&amp;rsquo;s the nature of the beast, and AI is only going to make it that much faster. Security can spend its time chasing apps around the internet, or it can build a road that’s quicker than the shortcut and safe from the moment something goes live to the day it’s switched off.&lt;/p&gt;
&lt;p&gt;In short, build a platform that enables them with these five principles:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Speed:&lt;/strong&gt; the safe path has to be faster than the shortcut, and built into the AI tools GTM already uses.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Safety:&lt;/strong&gt; safe by default, with risk deciding how apps are gated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sharing:&lt;/strong&gt; getting a demo in front of a prospect should be easy, and hard to leak.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lifecycle:&lt;/strong&gt; every app has an owner and an expiry date, so nothing is left running forever.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Visibility:&lt;/strong&gt; one place to see everything on the path, and to shut it down when needed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Get those right, and the safe path stops being the thing people go around. It becomes the way they work.&lt;/p&gt;</description></item></channel></rss>