AI security & AI governance

Use AI without losing control

Your teams already use AI, and perhaps your products do too. We make sure it happens securely, in line with data protection and fit for the AI Act: with clear rules for internal use and concrete safeguards for AI in your systems. Concrete risks, concrete measures, no hype.

€1,900
Entry point: readiness check at a fixed price
OWASP
LLM and ML security as the testing framework
ISO 42001
Governance that connects to ISO 27001
Dec 2027
AI Act high-risk obligations, with lead time from today

Sound familiar?

Four situations we currently see in almost every company.

"Our people already use AI. There are no rules."

GenAI assistants have arrived in daily work, often via private accounts and without approval. That is not misconduct by your teams; it is a sign that clear rules are missing. Shadow AI does not disappear through bans, but through good alternatives with guardrails.

"We don't know which data flows where."

Prompts contain customer data, source code and internal information. Without an inventory and clear rules you can guarantee neither data protection nor confidentiality, and chances are you only find out once something has happened.

"Our product uses AI. What do we need to protect it against?"

Prompt injection, data leakage through model outputs, manipulated training data, a vulnerable model supply chain: AI features bring their own attack surface that classic security testing does not cover.

"What does the AI Act require from us, and from when?"

Prohibitions, transparency obligations, high-risk requirements: which of these apply depends on how and where you use AI. The good news: the key deadlines are in 2027 and 2028. There is still time for a structured approach.

Two situations, two paths

Rolling out AI internally and building AI into products are different tasks with different risks. We cover both, separately or together.

Use AI securely inside your company

Governance for daily work: turning uncontrolled use into structured, productive AI adoption.

  • Inventory: which tools are in use, which data flows
  • AI policy and approval processes instead of shadow AI
  • Data protection and AI Act classification of your use cases
  • Training your teams for secure use

Your entry point: AI readiness & risk check, €1,900

Secure AI in your products

Security for AI features: understand the attack surface before others do.

  • Threat modeling based on the OWASP Top 10 for LLM applications
  • Protection against prompt injection and data leakage via outputs
  • Securing training data and the model supply chain
  • Security evidence for customers and regulators

Your package: AI security assessment, €6,400

How we help

From first overview to established governance, in clear steps and without a big-bang project.

Establish your baseline

The AI readiness & risk check creates clarity within days: which AI is in use, how it is classified under the AI Act and data protection law, and where your biggest risks lie.

Secure your systems

In the AI security assessment we model the threats to your AI applications based on OWASP LLM/ML and derive prioritised safeguards, technically concrete rather than abstract.

Anchor the rules

AI policy, approval processes and security gates in the development process: governance that works in daily practice and connects to ISO 27001 and ISO/IEC 42001.

Enable your teams

Workshops and developer enablement, so that secure AI use does not depend on two experts but becomes routine for your teams.

Our packages

Clear fixed price, defined scope, fast start. Each package can be booked individually.

Recommended entry point

AI readiness & risk check

€1,900

The baseline: we inventory your AI use, classify it under the AI Act and data protection law, and name your biggest risks.

  • Inventory of AI tools and use cases
  • AI Act and data protection classification
  • Top risks with prioritised measures
  • Delivered as a compact report

AI security assessment

€6,400

For AI in your systems and products: we model the threats to your AI application and derive concrete safeguards.

  • Threat modeling based on OWASP Top 10 for LLM/ML
  • Prompt injection, data leakage, model supply chain
  • Prioritised measures with implementation guidance

Secure AI coding enablement

from €4,900

Copilot, Cursor & co. safely in your development process: a clear policy, security gates and protection against hallucinated or malicious packages.

  • AI coding policy for your teams
  • Security gates in the development process
  • Protection against hallucinated and malicious dependencies
  • Hands-on developer enablement
Workshop

AI security / AI Act & governance

from €1,600

Bring your team up to speed: AI risks, AI Act obligations and governance, compact and practical.

  • Online or on site
  • For security, privacy and product teams
  • Tailored to your use cases

All prices excl. VAT. The entry point is deliberately lightweight: the readiness check takes a few days and requires no preparation on your side.

AI Act

The AI Act: deadlines with lead time

The AI Act arrives in stages. None of the deadlines is cause for panic, but governance and evidence need lead time.

  1. Feb 2025

    Prohibited practices

    The AI Act's prohibitions apply, for example against manipulative systems and social scoring. No practical impact for most companies.

  2. Aug 2025

    GPAI transparency

    Transparency obligations for providers of general-purpose models. Relevant mainly for model providers, less so for users.

  3. Dec 2026

    Labelling obligation

    AI-generated content must be labelled. Relevant for everyone who publishes GenAI content.

  4. Dec 2027

    High-risk obligations (Annex III)

    The requirements for high-risk AI under Annex III apply, after the postponement from May 2026. Affected are defined use cases such as recruitment or critical infrastructure.

  5. Aug 2028

    Product-regulated AI (Annex I)

    AI in product-regulated areas, including medical devices, must meet the high-risk requirements.

Start now and you work without time pressure: first overview and rules, then hardening, then evidence. Our packages are built in exactly that order.

Why ActSecure

AI security needs both: a technical understanding of the attacks and regulatory classification. We bring both.

Product security + regulatory

Security testing and development practice on one side, regulatory affairs and quality management on the other: we assess AI risks technically and classify them legally. Our partner Dan Gora is a reviewer of the OWASP Top 10 for LLM Applications.

Connects to your standards landscape

We build AI governance so that it fits ISO 27001 and prepares the path to ISO/IEC 42001, without parallel structures.

AI in medical devices

For MedTech we bring the combination of AI security and MDR experience: from the Annex I timeline to alignment with the conformity assessment.

You work directly with the specialists, without the overhead of a large consultancy.

FAQ

Frequently asked questions

Our employees already use private AI accounts. How do we rein that in?

In our experience bans do not work; they just push usage out of sight. The effective path: an inventory first, then a clear policy with approved tools and defined data classes, plus a short training. That turns shadow AI into controlled, productive AI use. This is exactly the core of our readiness check.

Does the AI Act even apply to us?

Very likely yes, but usually more mildly than feared. If you only use AI internally as a tool, your focus is on transparency and labelling obligations plus data protection. The high-risk obligations affect defined use cases (Annex III) and product-regulated AI (Annex I). Classifying your concrete use cases is part of the readiness check.

Do we need ISO/IEC 42001?

Not immediately, and not everyone. ISO/IEC 42001 is the management system for AI and becomes relevant mainly for larger organisations and in tenders. What makes sense today is building your AI governance so that it is 42001-ready, especially if you already have ISO 27001. Then the path is short later on.

What happens to our data when teams use GenAI tools?

That depends on the tool and the contract: with free consumer accounts, inputs may be used for training; business agreements usually rule that out. That is why tool selection, data classes and contract terms belong in the AI policy. In the readiness check we examine exactly that and give a concrete recommendation per tool.

We are building AI into our product. Is our existing security testing enough?

It is the foundation, but it does not cover AI-specific attacks. Prompt injection, jailbreaks, data leakage through model outputs or manipulated dependencies in the model supply chain follow different patterns than classic vulnerabilities. The OWASP Top 10 for LLM applications provides an established testing framework for this, and it is what we follow in the AI security assessment.

Let's talk about your AI use

In a free intro call we clarify where you stand and whether the readiness check is the right entry point. No strings attached, and no hype.

info@actsecure.eu