All insights
Threats 7 min read

Social engineering and prompt injection: a runtime problem

Prompt injection and social engineering against AI systems are not theoretical. Here is how the manipulation works, why it matters for regulated firms, and what runtime controls actually change.

Prompt injection is the practice of crafting inputs that push a model to ignore its instructions or reveal behaviour it should not. Social engineering applies the same intent to the people and processes around a model. Both target the live conversation rather than the code, which is why they slip past static reviews.

For regulated firms the risk is concrete: an assistant persuaded to give advice it should not, a support agent nudged into disclosing data, or a copilot coaxed into acting outside policy. The damage is not only technical — it is regulatory, reputational and operational.

Runtime controls change the picture because they inspect interactions as they happen. An independent layer can identify manipulation, decide against firm-specific policy, act by blocking or escalating, and evidence what occurred. Crucially, a person stays accountable for the outcome.

norse3 is designed to sit in exactly this position — model-agnostic, independent of the vendor, and focused on the conversational layer where these attacks land.

See where norse3 sits in your estate.

Book a walkthrough and see how the control and evidence path applies to your conversations.

Book a walkthrough

Cookie preferences

We use cookies to understand site usage and improve your experience. Manage your settings or accept all.