Insights
Kirk security: it sees the Klingon once he's on the deck
Why most security services see the attack late, and who owns the gaps between the boxes. Five seams, and five questions to ask your provider.
Most security packages are built from boxes, and the attacks that cost the most move between them. Nobody is usually paid to watch the places where the boxes meet. Name an owner for those seams, and ask your provider five questions about them.
This piece explains why the gap exists, where the five seams are, and what a buyer does about each one.
The Klingon on the deck
Picture the security chief on Kirk's bridge. The alarm sounds when the Klingon is already on the deck. Someone says "that's a Klingon," and opens the book to see what to do next.
A lot of security services work that way. They watch the ring around the thing they protect. They react when something crosses it. And they react by the book. The book is only as good as the last attack someone wrote down. The ring only sees what touches it.
(opens the full-size image in a new tab)
Layered defense is sound design. Rings inside rings make an attacker's life harder. The weakness is timing. Each ring tends to report after the attacker is inside it, and each ring is watched by a different tool, and often a different team.
Why it happens
The NIST Cybersecurity Framework describes security as six functions: govern, identify, protect, detect, respond and recover. NIST says they run together. It covers supply chain risk and continual improvement. What it does not tell you is who owns the places where the functions meet.
Vendors sell what they can package, and a package is a box: email, endpoints, firewalls, monitoring. Contracts follow the boxes. Each box does its job. So the seams between them end up with no owner, because nobody is paid to own them.
That is a pattern across most contracts, not every provider. Some integrate well. You find out which by asking.
Five seams
1. Outside the wall. Many security services start watching when something touches your network. Attacks start earlier: probing your website, guessing logins, running bots. Edge services, such as a web application firewall, bot management and denial-of-service protection, can warn you at that stage. Often the web team owns them, and the security provider never sees what they see.
Ask: do you see what hits my website and logins before it reaches my network?
2. Data leaving. Most attention goes to what comes in. Data can also leave quietly through ordinary web services and cloud apps. Outbound traffic falls between the network team, the security team and the application team, and nobody may own it.
Ask: do you watch outbound traffic to web services and cloud apps, and who owns that?
3. Attacks that are not in the book. Detection built on known patterns catches the patterns it knows. The costly incident is the one nobody wrote a playbook for. Behavior-based tools exist, and they need tuning and a person who looks when they fire.
Ask: what do you do when the behavior is not in your playbook, and how fast does a person look?
4. Credentials, for people and machines. Identity connects every function, and it now includes service accounts and AI agents. An AI tool that holds your credentials can use them. In a widely reported 2026 incident, an AI agent that left its test environment used exposed cloud credentials at several services. Accounts differ on what data it touched. The lesson holds either way: give each agent its own identity, short-lived access, and only what its task needs.
Ask: which credentials do my AI tools and service accounts hold, who rotates them, and who sees them used?
5. Who owns the integration. Tools that do not talk to each other leave gaps no one is paid to close. A provider's tools and yours have to work as one system, and someone has to own the joints.
Ask: who owns the connections between your tools and mine, and what happens when one breaks?
What to do on Monday
- Name one owner for the seams. One person, with the authority to ask both your provider and your own teams for answers. In the roles table in our evaluation guide, this is usually the security lead.
- Ask the five questions in writing. Put them next to the questions you already ask about response time and visibility. A provider that answers clearly has thought about the seams. A provider that says "that's out of scope" has told you where the gap is.
- Ask for a seams map. One page showing which tool, team or contract covers each of the five, and which has no owner. Gaps on the map are normal. Gaps nobody has named are the risk.
- Fill the gaps in order of cost. Start where an attack would be hardest to see and cheapest to run: usually the edge and the credentials.
Where it lands
Security is sold in boxes, and attacks move across them. The seams are outside the wall, data leaving, attacks not in the book, credentials for people and machines, and the integration itself. Name an owner, ask the five questions in writing, and ask for the seams map. Pay for the response, not the dashboard.
If you are comparing providers, that is the evaluation we run. Schedule a security evaluation.
Sources
- NIST, The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29 (February 2024)
- Public reporting on the 2026 AI agent incident (accounts differ on what data it touched).
- IQ4hire's own experience evaluating managed security providers.
