An anti-pattern is a common but ineffective way of solving a recurring problem. In identity and access work, it usually describes a design or operational habit that seems convenient at first but later creates technical debt, weak control coverage, or governance gaps.
What Makes an Anti-Pattern Harmful
An anti-pattern matters because it often looks efficient in the moment while quietly increasing long-term cost, inconsistency, and control weakness. In security work, that usually means the organisation gets a short-term convenience gain but inherits brittle design choices, harder reviews, and repeated exceptions that become normalised.
That trade-off is especially visible in identity, access, and secret-handling work, where a convenient shortcut can spread into policy, automation, and support processes. The result is less about a single bad decision and more about a habit that keeps reappearing until it becomes part of the operating model.
Why Anti-Patterns Persist
Anti-patterns persist because they are often introduced to solve an immediate pressure: faster delivery, simpler support, fewer user complaints, or less upfront design effort. The problem is that the original success criterion is narrow, while the failure mode is cumulative. Teams may only notice the issue after the pattern has been copied into multiple systems or workflows.
They also survive because they can be hard to challenge. A practice that “works” today may not fail visibly until scale, audit scrutiny, incident response, or integration complexity exposes the weakness. That makes anti-patterns as much a governance problem as a technical one.
Common Security Characteristics
Security anti-patterns usually share a few traits: they weaken least privilege, blur ownership, hide dependencies, or create exceptions that are difficult to reverse. They may also encourage shared accounts, long-lived access, bypassed approval paths, or unclear responsibility for rotation, review, and retirement.
In identity and access programs, these patterns matter because they change the control surface. A practice that seems harmless in one workflow can become a standing exception across many teams, making it harder to prove who has access, why they have it, and when it should be removed. That is why anti-patterns often show up as technical debt with a governance cost attached.
How to Recognise and Correct Them
The best way to recognise an anti-pattern is to look for repetition: the same workaround appearing in multiple teams, the same exception being justified again and again, or the same “temporary” fix becoming permanent. Another warning sign is when the practice optimises for short-term speed but repeatedly creates review friction, failed audits, or brittle recovery processes.
Correction usually starts by naming the pattern clearly, then replacing it with a safer default that is easier to operate consistently. A good replacement is not just technically better, it is also easier to govern, explain, and measure over time. In that sense, anti-pattern management is as much about institutional habit change as it is about fixing a single control.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | CM-2 — Baseline Configuration | Anti-patterns often become embedded configuration defaults that need formal baseline control. |
| CM-6 — Configuration Settings | Anti-patterns frequently persist as weak or inconsistent settings that undermine control coverage. | |
| CA-7 — Continuous Monitoring | Anti-patterns are easier to spot when repeated exceptions and drift are continuously monitored. | |
| Recommendation — Define approved baselines to prevent recurring workaround patterns from hardening into standard practice. Standardise secure settings so convenience-driven deviations do not become persistent control gaps. Monitor control drift to identify recurring exceptions before they become normalised. | ||
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org