You’ve kept this thing running for a long time.
Vendors changed. Org charts got shuffled. Traffic moved, SaaS showed up, so somebody decided “cloud-first” was a personality trait. Yet somehow, most days, the critical stuff still works.
That’s not luck. That’s experience, and probably a few strategic Timmies runs.
The problem isn’t effort. It’s fragmentation.
Network sees one truth. Security sees another. Ops sees tickets. Leadership sees risk and a piling queue, usually after the fact. The thesaurus has a lot of synonyms for “silo,” and none of them are flattering.
When something breaks, the first question isn’t “how do we fix it?” It’s “whose problem is this?”
Where this usually falls apart
This pattern shows up for familiar reasons:
- tools don’t talk, or they talk in polite summaries that hide the meaty parts
- identity is bolted on instead of built in
- policy lives in Word docs instead of systems
- exceptions pile up, then become the architecture
- audit trails feel more like archaeology than evidence
None of it is malicious. Most of it started as “just for now.” Then Gary took a new role, the ticket never got closed and everyone became afraid to touch the one process nobody fully understands anymore.
That’s how environments get haunted. Not the fun kind with candles and a Victorian backstory, the kind where every change request comes with a warning label.
Who ya gonna call
What actually helps: run network and security as one operating motion
One intake. One triage. One backlog. One view of what changed, who touched it and why it was allowed.
Not “another dashboard.” Actual shared ownership.
This is where Kyndryl Bridge earns its keep. That includes the usual suspects, Cisco and Meraki, HPE Aruba, Fortinet, Palo Alto, plus the workflow layer (ServiceNow) so “visibility” turns into owned work, not screenshots and folklore. It’s designed to consolidate signal across a messy estate, then turn it into actionable insights at scale. [source] Kyndryl’s own numbers show over 16 million AI-driven insights monthly and productivity benefits approaching $3 billion a year, which is a nice way of saying teams spend less time hunting for context and more time fixing the thing that’s on fire.
And it doesn’t really care whether the estate is Cisco Meraki, HPE Aruba Networking, Fortinet or a mixed bag held together by screenshots and folklore. The point is still the same: one place to see what’s real, before the next “quick exception for Gary” becomes everyone’s Friday night plans. [source]
ISM’s role is making that usable in a Canadian environment. Tools are global. Delivery has to work with your org structure, your compliance reality and your Tuesday afternoon change windows.
What gets better
When this sticks, a few quiet improvements emerge:
- incidents resolve quicker because less time is spent figuring out what changed
- audit questions get answered with evidence, not meetings
- fewer handoffs, fewer escalations, fewer “it must be the firewall” reflexes
- migrations stop turning into surprise archaeology digs
- calendar invites from Gary aren’t so bad
Nothing flashy. Just fewer unnecessary flames, and fewer people playing firefighter.
What to fix first
Catalogue what you have Map your services, agree on ownership, and define what “normal” looks like before you try to improve anything.
Build privacy into daily work Logs and operational data need residency, access control and lifecycle rules, not wishful thinking.
Operationalise governance Make policy enforceable, logged and reviewable. Expire exceptions by default.
Secure the data itself Identity is the bouncer, but the data still needs locks, labels and monitoring.
If you’re already on good platforms, Cisco Meraki, HPE Aruba, Fortinet, pick your flavour, and it still feels like a daily game of telephone, that’s not a vendor problem. That’s a visibility and ownership problem.
ISM’s value here is turning those platforms into an operating model your teams can actually live with: one intake, one backlog, fewer blind spots, cleaner evidence. Kyndryl brings the global muscle and repeatable service patterns. ISM keeps delivery grounded in Canadian reality and accountability.
