There’s an previous management fantasy that goes one thing like this: The CISO surveys a sprawling know-how property, discovers 11 instruments doing the work of 4, calculates the licensing financial savings, selects a shiny new strategic platform and declares that consolidation has begun. Six months later, all 11 instruments are nonetheless working. The brand new platform is now quantity 12.
I’ve seen variations of this all through my profession, from monetary providers to media to know-how firms. At CME Group, I ultimately gave myself an unofficial title: chief decommissioning officer. The job was significantly much less glamorous than the acronym steered. I needed to discover know-how that had overstayed its welcome, determine who believed they nonetheless owned it, decide who really relied on it and, often, put a bullet in its head.
Shopping for know-how is straightforward. Killing know-how is difficult. Software sprawl is never only a know-how drawback however somewhat an organizational psychology drawback. The business’s resolution has historically been consolidation. Purchase a platform. Standardize the stack. Scale back distributors and centralize procurement. Whereas all smart concepts, consolidation efforts routinely stall someplace between the PowerPoint slide and manufacturing.
Why? As a result of altering the toolset is straightforward. Whereas altering mindset is much tougher.
You can not Jedi thoughts trick an engineering group
Executives like what known as the “message from the highest.” The CEO says safety issues. The CIO says everybody will standardize. The CISO broadcasts the strategic platform. Procurement renegotiates contracts. In the meantime, Gartner produces a quadrant that reassures all people that the chosen vendor inhabits the right geometric area. All is properly on the planet of golf course nepotism.
Then actuality arrives. A developer says the brand new scanner takes 12 minutes longer. A advertising supervisor has a revenue-generating legacy API they rely on. Exception requests have been filed for a number of years to permit this instrument to live on regardless of the packages supporting it being end-of-life and receiving no safety updates. That is the place the “message from the center” issues.
Transformation doesn’t occur solely in boardrooms and fusion groups. It occurs within the layer of engineering managers, architects, product house owners, safety engineers and operations leaders who decide whether or not the coverage introduced upstairs turns into the conduct practiced downstairs. Each layer of the org chart is ostensibly making an attempt to do the precise factor and make issues higher. However top-down politics and bottom-up initiatives seldom discover each other standing on widespread floor.
Ignore the center layer of the org chart and your consolidation challenge turns into a somewhat costly train in shelfware. That is one thing I realized working in European organizations, the place consensus constructing carries extra organizational weight than the command-and-control instincts widespread in American companies (the Nike-inspired administration philosophy of “Simply Do It!”). You will have the authority to decide with out possessing the organizational permission (or “rubber meets the highway” context) required to make it stick or worthy of implementation.
Good chief decommissioning officers want a combination of Jedi and Machiavellian abilities. We’d like persuasion, coalition constructing, incentives, selective strain and infrequently the power to persuade folks that the concept you desperately want them to help was their thought all alongside. These are, in reality, the droids you’re searching for.
Each instrument comes with an id
The Star Wars metaphor turns into extra helpful after we cease considering of safety merchandise as software program. Fashionable safety instruments have volition and intent. They’ve:
- API keys
- Service accounts
- OAuth grants
- Cloud permissions
- GitHub entry tokens
- CI/CD integrations
- Slack bots
- Webhooks
- Database credentials
- Kubernetes roles
- Machine identities and,
more and more, AI brokers are performing with pervasive and chronic delegated human authority.
Each time we introduce safety merchandise, we start one other extremely privileged account. The business talks endlessly about human id. Who is that this particular person and what are they allowed to entry? We’re decidedly a lot much less disciplined about delegated id. What is that this utility allowed to do on behalf of Mike? What is that this scanner allowed to learn from GitHub? What repositories can this integration modify? Which credentials did we give the previous vendor three years in the past? And the more and more vital query: when an autonomous agent acts, whose authority is it really exercising? This adjustments the economics of instrument sprawl. The price of the twelfth safety instrument shouldn’t be merely one other annual subscription. It’s one other (doubtlessly misbegotten) belief relationship.
This is the reason I’m advocating decommissioning as a core safety self-discipline. Know-how organizations undergo from an immortality bias. I gave a “Prime-Rated Session” on this subject at RSAC within the spring. Now we have refined processes for creating issues and surprisingly primitive processes for making them disappear. The software program growth lifecycle is normally illustrated as planning, design, growth, testing and deployment. The diagram usually ends there, as if each utility ever deployed subsequently lives fortunately ever after. It doesn’t.
Consolidation with out decommissioning is multiplication
I’m skeptical when distributors promise “platformization” will resolve instrument sprawl by itself. A platform technique can completely make sense. Fewer distributors can imply decrease licensing prices, fewer integrations and constant information with much less operational complexity. However buying a platform doesn’t consolidate something by itself. Eradicating the previous programs does. That sounds apparent, but many organizations measure profitable consolidation by contracts signed somewhat than programs eradicated.
Think about changing three instruments with one platform however leaving all three merchandise technically operational “quickly.” The service accounts stay. Somebody nonetheless logs into them. Congratulations! You’ve not consolidated 4 instruments into one however as an alternative consolidated three instruments into 4. This distinction turns into vital as safety merchandise acquire autonomous capabilities. Yesterday’s forgotten dashboard turns into tomorrow’s forgotten agent with permission to take actions. A zombie utility is unhealthy sufficient, however a zombie utility with company is worse.
Ask the individuals who really use the droids
The antidote shouldn’t be stronger central management however somewhat express possession. RACI matrix a lot? Earlier than changing a instrument, discover the individuals who use it and ask an embarrassingly easy query: “What do you really use this for?” Don’t ask what the contract says. Don’t belief what the structure diagram would possibly present (*do* examine the final modified date, although).
Take what the seller’s customer-success consultant believes with a grain of salt and greater than a modicum of skepticism. What do folks really do with it on Tuesday morning? Safety leaders are normally shocked by the reply. Perhaps the vulnerability scanner’s major worth shouldn’t be vulnerability scanning. Maybe an engineering group is determined by an obscure export operate for its weekly metrics. Perhaps the previous SIEM has one correlation rule tied to a regulatory requirement that hasn’t been migrated. You can see this stuff when you look.
That is the place the center of the group turns into your actual intelligence community. The folks closest to the programs know the place the undocumented dependencies stay. Handled as obstacles and so they’ll defend their instruments. However enable them to be members and so they’ll assist dismantle them. A great perspective when planning to kill somebody’s child is to assist them perceive that they fell in love with the management the instrument gave them over the chaos that reigned earlier than it was carried out. And {that a} new instrument might be equally snug and simpler to help than the burden of the care and feeding that almost all “heritage” (I favor this time period to “legacy”) functions and options require.
Possession ought to embrace the facility to advocate retirement. One of many healthiest metrics a corporation may create: variety of instruments and integrations it efficiently eradicated this yr. We have fun deployment. Why don’t we have fun deletion?
The CISO as chief decommissioning officer
Each CISO must spend time as CDO. Not chief information officer. Chief decommissioning officer. The position requires asking uncomfortable questions as a result of virtually each incentive in know-how encourages addition. No person will get a press launch or a promotion for turning one thing off. However resilience is partly subtractive.
Each redundant vendor eliminated is one much less firm holding your information and one much less administrative console an attacker can goal and breach. Our business spends billions asking, “What else ought to we deploy?” Mature organizations additionally ask, “What can we safely eradicate?” That second query turns into way more vital with agentic AI.
We’re quickly filling enterprises with digital droids performing on behalf of people. No matter operate, virtually all require credentials and delegated authority. Organizations that handle this transition efficiently is not going to merely know the way to authorize these identities; they are going to rotate and revoke them mechanically. Management subsequently wants each a message from the highest and a message from the center. The highest establishes path and the center provides actuality.
Deliver the folks doing the work into the choice. Be certain that your fusion group tasked with consolidating 77 dashboards is comprised of previous guard leaders in addition to younger blood new hires. Attempt to grasp the dependencies, practical necessities (antiquated as they could be) and non-functional necessities similar to availability, integrity and confidentiality. Outline what profitable retirement seems like earlier than shopping for the substitute.
Don’t ‘transfer alongside’
The following time somebody arrives with a miraculous new platform promising to eradicate half of your stack, resist the urge to wave your hand and say, “These aren’t the droids we’re searching for.” They could be. However earlier than shopping for extra droids, discover out who owns those already wandering round your Demise Star. Discover them. Identify them. Perceive what authority you gave them. And when their mission is completed, dare to change them off. Create a know-how graveyard in your wiki, Confluence or SharePoint website and have fun the addition of decommissioned instruments and applied sciences with much more fervor than these which have only in the near past sprung into existence.


