Topic starter
05/07/2026 6:56 pm
TL;DR: AI security teams are repeating the pre-AlexNet mistake by relying on static filters, manual test cases, and pattern matching against systems that evolve faster than handcrafted rules, according to Lakera. The real risk is that yesterday’s control model cannot generalise to dynamic AI behaviour, so governance must move from exception-chasing to adaptive assurance.
Editorial analysis by NHI Mgmt Group, based on content published by Lakera: “What the AI Past Teaches Us About the Future of AI Security”.
Key questions
Q: What breaks when AI security relies on static prompt rules?
A: Static prompt rules break when the same unsafe intent can be expressed through new wording, context, or sequencing.
Q: Why do static guardrails create false confidence in AI security?
A: They can block obvious prompts while leaving rephrased, indirect, or chained attacks untouched.
Q: What are the signs that AI assurance is too narrow?
A: The clearest sign is when teams only test model accuracy or prompt behaviour while ignoring data integrity, provenance, access control and monitoring.
Practitioner guidance
- Replace prompt-only guardrails with behaviour-based detection Use signals such as instruction escalation, repeated boundary probing, tool abuse, and abnormal context shifts to identify unsafe interactions.
- Build adversarial test coverage for rephrasing and context shifts Expand evaluation beyond fixed jailbreak examples to include paraphrase variation, indirect instruction paths, and chained prompt manipulation.
- Separate policy enforcement from safety assurance Treat written policy as governance intent and model-driven monitoring as operational assurance.
Bottom line: AI security breaks down when teams mistake static prompt filters for a durable defence model.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
05/07/2026 7:19 pm
Rule-based AI security is a control model mismatch, not a tuning problem. The article’s central point is that dynamic model behaviour outpaces handcrafted policy logic by design. That is not a matter of improving the rule set, but of recognising that the control philosophy no longer matches the attack surface. Practitioners should read this as a signal to stop treating prompt filtering as the primary security boundary.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: How can security teams tell whether AI lifecycle controls are working?
A: They should look for evidence that access requests, policy enforcement, and usage visibility are centrally recorded and current. If those signals are fragmented across platforms, the programme may be documenting governance rather than enforcing it. Continuous traceability is the practical test.
👉 Read our full editorial: AI security is repeating the old rule-based failure pattern