A SaaS? platform that continuously tests LLM? apps, agents, MCPs, and AI workflows for prompt injection, data leakage, and adversarial abuse.
Added Jun 9, 2026
Last signal 16h ago
Companies building LLM?-backed applications are hiring specialized security engineers to manually assess prompt injection, model abuse, data leakage, and risks across agents and AI stack components. These threats are new, fast-moving, and hard to validate with traditional application security tools, especially when systems are non-deterministic and connected to enterprise data or tools.
The product provides automated offensive testing for AI-enabled systems, including red-team scenario generation, prompt-injection probes, agent abuse simulations, data-exfiltration checks, and model/API? boundary testing. It produces actionable risk reports, regression tests, and trust-layer policy recommendations that security and AI engineering teams can run before launch and continuously in CI/CD.
Enterprises are rapidly deploying LLM? APIs?, self-hosted models, agents, MCPs, and AI-powered features while job postings show a clear need for dedicated AI security expertise. Security teams need repeatable tooling because hiring offensive AI security specialists does not scale across every product team and release cycle.
59
100% score confidenceShowing 1-20 of 20 signals
Support the deployment and evaluation of cybersecurity platforms and tools such as Mythos , vulnerability management, and security assessment solutions. Experiment with LLMs, RAG systems, prompt engineering, and agent-based workflows.
Build detection at scale. Design and ship security workflows that combine deterministic analysis (taint, reachability, static slicing) with LLM reasoning to find real vulnerabilities (SSRF, IDOR, injection, auth gaps, supply-chain risk, and beyond) across many languages and frameworks. Make LLMs viable for security-critical work. Engineer agentic pipelines and prompts that are precise, cost-aware, and trustworthy: atomic, well-scoped steps grounded in deterministic context, with attention to hallucination, confidence calibration, and which models see sensitive code.
Own end-to-end test strategy and execution for AI/ML models, GenAI, LLMs, and multi-agent systems, spanning functional, adversarial, safety, and security testing. Design evaluation frameworks to measure hallucination rate, bias, toxicity, and prompt-response consistency.
Personally, I'd go beyond traditional security scans if the SaaS includes AI agents or LLM features. I'd want to test things like prompt injection, excessive permissions, data leakage, and how the system behaves when interacting with external tools, not just conventional web vulnerabilities. It also seems like more teams are looking at runtime security as part of that process, and I've heard that some companies like NeuralTrust focusing on monitoring and enforcing policies once AI features are actually in use, rather than only before deployment
Build reusable AI security primitives such as guardrails, scanners, policy checks, tool-use controls, registries, sandboxes, libraries, and workflow-native enforcement points. Design security tooling that can sit in the inference, retrieval, or execution path to detect and prevent prompt injection, jailbreaks, tool misuse, data leakage, unsafe code generation, and suspicious agent behavior.
+17 more signals