CRA for mobile apps.

Selling an app or connected product in the EU? Find and fix its vulnerabilities in time for your CRA technical documentation, and keep your app tested across its support period.

For teams shipping mobile apps, and for manufacturers of connected products with a companion app.

The Cyber Resilience Act covers most products with digital elements placed on the EU market. That includes mobile apps and their integral remote data processing, for example the backend you build for your product and without which the app could not perform one of its functions. From 11 December 2027, those products must meet the essential requirements in Annex I:

  • Product security (Part I): among other requirements, the product is made available without known exploitable vulnerabilities.
  • Vulnerability handling (Part II): the manufacturer documents components in a software bill of materials (SBOM) and applies effective and regular tests and reviews of the product's security.

Annex VII requires your technical documentation to include reports of the tests carried out to verify conformity with these requirements. Without that evidence, you cannot complete the conformity assessment and affix the CE marking.

Depending on your product, testing can cover:

  • The Android or iOS app, with findings mapped to applicable Annex I requirements.
  • Backend interfaces the app relies on, within the agreed scope.
  • Interfaces with a connected device, such as Bluetooth, where the app is part of a connected product.
  • Third-party components shipped in the app: we review your SBOM, or help you generate it if you do not have one yet, and analyze which of the known vulnerabilities are actually exploitable in your app, so you fix the real risks instead of updating every flagged dependency.
  1. Call: you tell us about your app, the product it belongs to and what your technical documentation is missing.
  2. Proposal: we set out the agreed scope, how often to test, what we need from you, the schedule and a fixed price.
  3. Testing: you send us the builds and we start. If we find something critical, we let you know right away.
  4. Report and review: we send you the report and go through it with your engineers.
  5. Retest: once you have fixed the vulnerabilities, we confirm they are resolved and send you a new version of the report for your technical documentation.
  6. Recurring testing: across the support period, we test the releases we agree on and analyze the known vulnerabilities in the components of each one.

Technical report

States what we tested: the app on each platform, the build and the interfaces in scope, and the result for each applicable Annex I requirement, whether or not we found vulnerabilities. Every finding includes evidence, reproduction steps, impact, a CVSS score and vector, CWE and OWASP MASWE references, and how to fix it.

Third-party component analysis

We review your SBOM, or help you generate it if you do not have one yet, and tell you which known vulnerabilities are actually exploitable in your app (a VEX analysis) and how to fix them, so a flagged CVE does not force you to rebuild a product it never reaches.

Executive summary

Covers the scope and build tested, the results and the priorities, for management and non-technical readers.

Retest report

If you include the retest, we send a new version of the report with the status of each finding on the new build, so your technical documentation reflects the fixed version.

We know how a test report is reviewed

Our team comes from security certification laboratories, with experience in schemes such as Common Criteria, EMVCo SBMP and LINCE. That is why we write reports with their reviewers in mind: your own team and, if it comes to that, a notified body or a market surveillance authority.

We contribute to OWASP MAS

We map your tests to OWASP MASVS and MASTG, the standard and testing guide our team helps write. The same specialists who contribute to the standard test your app. OWASP recognized this work by naming vulnit an OWASP MAS Advocate.

Testing across the support period

The CRA expects regular testing, not a one-off report. We test each release you agree with us, explain how to fix what we find and, if you include the retest, check the fixes.

Meet the team
When do the CRA obligations apply?

Reporting obligations for actively exploited vulnerabilities and severe incidents apply from 11 September 2026. The essential requirements and conformity assessment apply from 11 December 2027.

Do we need a notified body?

Most mobile apps fall into the default category, where the manufacturer can self-assess. Some products are important or critical, for example smart home products with security functions such as locks or cameras, and may require a different route, including third-party assessment. The product's function and classification determine the route. We are not a notified body; we produce technical test evidence for your assessment. See the European Commission's conformity assessment guidance.

We don't know yet what the CRA requires for our product. Can you help?

Yes, we start there. In the scoping call we look at what applies to your product and which tests your technical documentation needs. If you need more support before testing, we can start with a consulting engagement and plan the testing afterwards.

What do you test against?

We map the agreed tests to applicable Annex I requirements, using OWASP MASVS and MASTG as mobile security references. We contribute to OWASP MAS and track relevant CRA harmonized standards as they are adopted.

How is this different from a pentest?

This service includes a penetration test of your app, the analysis of your SBOM and a report built for your technical documentation, with the result for each applicable Annex I requirement. If you do not need to comply with the CRA, a mobile application penetration test is enough.

What if we don't have an SBOM?

We help you generate it. If you already have an SBOM or a list of the libraries and SDKs the app uses, we start from there. Either way, we review it for known vulnerabilities and analyze which ones affect your app.

The SBOM flagged known vulnerabilities. Do we have to update everything?

Usually not. A CVE in a library does not mean your app is exploitable: it depends on whether your app actually reaches the vulnerable code and how it uses the component. We analyze each known vulnerability for real exploitability in your app (a VEX analysis, Vulnerability Exploitability eXchange), so you fix the ones that are a genuine risk and document the rest as not affected, instead of rebuilding the product over CVEs that never reach it.

What do you need from us?

The app builds (APK or AAB for Android, IPA for iOS), test accounts and access to the environment you prefer, whether production or a staging environment. If you have an SBOM, send it to us; if not, we help you generate it. The proposal sets out the details.

Do you need source code?

It is not required. If you share it, we review it too.

Do you test on physical devices?

When needed. On Android we mainly work with Chameleon, our analysis environment: it gives us deep visibility into what the app does in the operating system, and handles root, pinning and anti-instrumentation checks at the OS level by default. If we hit a limitation that matters for your app, we use physical devices. On iOS we use physical devices.

Do you use AI on my app?

Yes, to cover more of your app and go deeper in the same time. We use AI providers that do not train their models on your data. We only use accounts you provide or that we create ourselves, never other real users' accounts. Our specialists lead the work and validate every result. If your policy does not allow external AI, tell us when we agree on the scope and we work without it.

How long does it take and what does it cost?

It depends on the number of apps and platforms, their complexity (for example custom cryptography or hardware features such as Bluetooth or the camera), the backend interfaces in scope and the testing cadence. We send you a proposal with a fixed price and the schedule. It usually takes one to two weeks per platform, report included, depending on the complexity of your app. We can usually start the same week you accept the proposal; the start date depends on our team's workload and is stated in the proposal.

Is retesting included?

Retesting is quoted separately at a reduced rate. In the proposal we give you two options, testing only or testing with one retest round, so you know the total cost from the start.

Do you offer recurring contracts?

Yes. If you plan your testing across the support period with us, we agree special conditions for the whole period.

What format do the findings come in?

You receive one report per platform, with every finding detailed. If you also want to use them in your own tools, we provide them as CSV or JSON too.

What language is the report in?

English by default. If you need it in Spanish, just tell us.

How do you handle confidentiality?

We agree confidentiality terms before you share builds or documentation. We have a standard NDA, but if you prefer to use yours, we are happy to review it.

Tell us about your app and the product it belongs to. We reply within one business day to arrange a scoping call.

Talk to our team

A necessary cookie remembers your choices for up to 180 days. Privacy policy.