Policy · Security

Coordinated vulnerability disclosure policy.

Found a vulnerability in an Appfront system or service? Report it to us through a coordinated process. We treat every serious report confidentially, thank researchers acting in good faith, and take no legal action against responsible reports that stay within this policy.

Policy typeCVD / Responsible disclosure
Reporting channelsecurity@appfront.nl
PGPOn request
AcknowledgementWithin 5 working days
DisclosureCoordinated
VersionMay 2026

Our commitment to researchers.

Appfront develops software for clients in finance, healthcare and industry, among other sectors. Security is an ongoing responsibility, not a static state. We value the work of external researchers who help us find vulnerabilities before they can cause harm. This policy describes how to report a vulnerability to us responsibly, what you can expect from us and which legal frameworks apply.

We follow a coordinated vulnerability disclosure (CVD) model in line with the guidelines of the NCSC, the DIVD and ENISA. This means that reporting, investigation and publication are coordinated, with the aim of fixing vulnerabilities as quickly as possible without putting users, clients or third parties at unnecessary risk.

We take no legal action against researchers who comply with the rules of this policy. We regard responsible reports as a service to us, our clients and the wider internet infrastructure. If you have questions about how this policy applies to a specific investigation, you can put them to security@appfront.nl beforehand.

This policy is a living document. We update it when legislation, infrastructure or insights from security research call for it. Changes are published here on this page, with the version date. For clients and auditors who wish to cite this policy in a vendor onboarding or risk assessment, the version that appears on this page at the time of consultation applies.

security@
Central reporting channel for vulnerabilities
PGP
Encryption supported, fingerprint on request
Safe harbour
No legal action for responsible research
Hall of Fame
Public recognition for reporters, if desired

Scope: what falls under this policy?

01
In scope

appfront.nl and subdomains

The public production website, marketing subdomains and publicly accessible applications operated by Appfront B.V. This also includes API endpoints and authentication flows on these domains.

02
In scope

Infrastructure managed by Appfront

Cloud environments, build pipelines and deployment channels that we manage for our own services. This includes publicly accessible configuration or supply chain components that directly affect our software.

03
Out of scope

Client systems and third-party SaaS

Systems belonging to our clients (even if we built them) fall under that client's policy. Third-party services such as Google Workspace, HubSpot or GitHub fall under that vendor's policy.

04
Out of scope

Non-public and test environments

Internal endpoints that are not publicly accessible, staging environments behind authentication and local development environments are out of scope, unless you gained access unintentionally and report it to us yourself.

Which types of vulnerability do we welcome?

Category 01

OWASP Top 10 classes

Injection (SQL, command, LDAP), broken access control, broken authentication, server-side request forgery, insecure deserialisation and all other vulnerability classes in the current OWASP Top 10 for web and API.

Category 02

Authentication and authorisation

Authentication bypass, session fixation flaws, privilege escalation, multi-tenancy leaks, IDOR flaws and weaknesses in two-factor or single sign-on implementations on systems we manage.

Category 03

Supply chain and infrastructure

Vulnerable or misconfigured dependencies, insecure build or release pipelines, leaks of credentials or secrets in public artefacts, and infrastructure misconfigurations that enable exploitation.

What we ask of you as a researcher.

Responsible research protects both you and our users. Please follow the ground rules below, so that your research stays within our policy and within the legal framework of acting in good faith, including the ISO 27001 guidelines we follow.

No DoS or denial-of-service

No load testing, no flooding, no tests that affect availability.

No mass scanning

No automated scans with high frequency or broad payload sets.

No exfiltration of customer data

A proof of concept is enough. Stop at the minimum evidence needed.

No social engineering

No phishing or pretexting of employees, customers or suppliers.

No physical attacks

No attempts to gain access to offices, data centres or equipment.

Respect privacy

Do not view, copy or store personal data of third parties.

No backdoors

Do not leave backdoors, malware or persistence in our systems.

Confidentiality

Only make your finding public once we have jointly agreed a date.

How to report to us.

Step 01 · Send your report

Email security@appfront.nl

Email your finding to security@appfront.nl. For sensitive content, you can request our PGP fingerprint and encrypt your message. For urgent matters, you can copy fabian.vandijk@appfront.nl in parallel.

Step 02 · What to include

Reproducible description

Provide a clear description of the vulnerability, reproducible steps, your estimate of the impact, any screenshots or log lines, and a suggested mitigation. Please also state whether you would like public recognition.

Step 03 · First response

Confirmation within 5 working days

You will receive an initial confirmation from our security team within five working days. We validate the finding, determine its severity and agree with you how we will keep you informed of progress until publication.

What you can expect from Appfront.

01
Confirmation

First response within 5 working days

An acknowledgement of receipt with an initial severity assessment. For serious findings, we will generally respond sooner. No automated no-reply.

02
Progress

Updates in proportion to severity

We keep you informed of the progress of the investigation and the fix. There are no predefined deadlines: pace and detail depend on impact, complexity and third-party dependencies.

03
Disclosure

Coordinated publication

Publication only takes place once the fix is in production. In line with international practice, we apply a reasonable period after confirmation, with room to deviate by mutual agreement for complex supply chains.

04
Recognition

Hall of Fame, if you wish

Researchers who have helped us and would like public recognition will be listed in our Hall of Fame on this page. You may also remain anonymous; we will respect your choice.

Legal and normative framework.

Framework 01

Good-faith research

Article 138ab of the Dutch Criminal Code (computer trespass) does not rule out responsible security research if it is proportionate, targeted and reported. Research within the rules of this policy will not lead to a criminal complaint from Appfront.

Framework 02

NIS2 and Wbni

The Dutch Network and Information Systems Security Act (Wbni) and the European NIS2 Directive require appropriate security measures and reporting of serious incidents. A coordinated vulnerability disclosure (CVD) process is a logical part of this.

Framework 03

GDPR and DORA

For reports that involve personal data, we follow Articles 33 and 34 of the GDPR for data breach notifications. For financial customers, the European DORA Regulation is relevant; we coordinate with them where applicable and ensure alignment of timelines and communication to regulators.

How we handle reports internally.

A report sent to security@appfront.nl is read only by staff involved in handling it. We apply a need-to-know principle: technical details are shared only with colleagues or clients who are needed to validate, replicate and fix the vulnerability.

After an initial validation, we classify the finding by severity (low, medium, high, critical) and by the party that owns the affected system. For our own systems, we schedule the fix based on that classification. For findings that affect a client or a client's systems, we inform the client concerned in confidence, within the scope of our contractual agreements, and coordinate with them rather than publishing unilaterally.

Communication with the reporter takes place in the same email thread, preferably in the same language as the original report. For critical findings, we may ask you to be available for a brief technical verification. Once a fix has been rolled out, we will let you know and discuss any coordinated publication.

What applies in specific situations?

Not every case is the same. The scenarios below will help you judge where your finding fits within this policy and what a reasonable next step is.

Active exploitation observed

Report it immediately, including outside office hours. We escalate internally to incident response.

Finding in a client system

We inform the client concerned in confidence and coordinate with them.

Personal data seen

Do not keep or share anything, and mention it in your report. Together, we will assess the GDPR impact.

Gained access unintentionally

Stop immediately, do not collect any further data and report it. No sanction applies if you acted in good faith.

Bug bounty platform

Appfront does not currently run an active bug bounty platform; we accept direct reports.

Cash bounty

No cash reward as standard; in cases of exceptional impact, we will discuss tailored recognition.

Press or third parties

Please refer enquiries to security@appfront.nl. We keep communication coordinated.

Compliance auditor

Clients and auditors can cite this policy as evidence for vendor onboarding.

Hall of Fame.

Open invitation

Place reserved for the first reporter

We would be glad to list the name or pseudonym of researchers who have helped us here, once the first responsible report has been handled and the reporter wishes to be publicly acknowledged.

Anonymity possible

Listing on your terms

You decide whether your contribution is made visible and under what name. We do not list researchers without their explicit consent, and we use a minimal set of information.

Coordination

In line with the NCSC and DIVD

For reports that come in via a coordinating body, such as the NCSC or the DIVD, we follow their acknowledgement and communication protocol and align our publication with it.

Frequently asked questions.

What exactly is a CVD policy?
A coordinated vulnerability disclosure (CVD) policy describes how an organisation wants external researchers to report vulnerabilities, how it handles such reports and how publication works. It is a practical application of the international responsible disclosure standard recommended by bodies including the NCSC and ENISA. The aim is for flaws to be fixed before they are exploited, without the reporter facing legal consequences.
Who can report a vulnerability to Appfront?
Anyone: independent security researchers, students, clients, suppliers, other agencies or members of the public who simply stumble across something. You do not need any relationship with Appfront to qualify for the safe harbour in this policy. We do ask that you follow the rules set out above and send your report directly and exclusively to us, rather than to third parties or the press.
Do I have to disclose my name when I report?
No. You can report under a pseudonym or completely anonymously. Bear in mind that anonymous reports make it harder for us to ask clarifying questions or keep you updated on progress. We keep contact details to a minimum, use them only to handle the report and will not publish your identity without your explicit consent.
Will I receive a cash bug bounty?
Appfront rewards reports with recognition rather than a cash bounty. We currently have no fixed amount per severity category. For findings with exceptional impact, we will discuss a tailored form of recognition with you. What we always offer: confidential handling, a serious technical dialogue and public recognition in our Hall of Fame if you would like it.
How long does it take for a fix to reach production?
That depends on the severity, the nature of the vulnerability and any third-party dependencies. A misconfiguration in one of our own systems can often be fixed quickly; a supply-chain issue involving several parties takes longer. We work to a reasonable period before publication, in line with international CVD practice, and will agree a different timeline with you if the complexity requires it or if the vulnerability is being actively exploited.
Can I publish my findings myself?
Yes, but only once we have jointly agreed a date and the fix is in production. Premature publication without coordination falls outside the scope of this policy and can worsen the risk position of customers or end users. We are happy to work with you on a joint advisory or a coordinated post that brings together your research and our remediation measures.
Which customers or auditors ask for a CVD policy?
Mainly financial institutions, healthcare providers, semi-public organisations and large corporates ask during vendor onboarding whether a supplier has a demonstrable CVD or responsible disclosure process. For customers with ISO 27001, NEN 7510, SOC 2 or DORA obligations, this policy is relevant material for their own compliance file.
Does this policy also apply to software Appfront has built for my organisation?
Not automatically. The custom software we build for clients generally runs under that client's responsibility and on their infrastructure. This means their security policy and reporting process take precedence. If desired, we help our clients set up their own CVD (coordinated vulnerability disclosure) policy; contact us via /contact.

Found a vulnerability?

Send your report to security@appfront.nl. We treat every serious report confidentially and acknowledge receipt within five working days. For encrypted communication, you can request our PGP fingerprint via the same address.

Confirmation within 5 working days
Confidential handling
Westerdoksdijk 599, Amsterdam

Edit content