Evidence for your auditors
Watchdog keeps your compliance evidence up to date at every survey.
Rules such as NIS2, DORA and the Cyber Resilience Act, and standards such as WCAG and OWASP ASVS, ask a company to show evidence of how its software is built and protected. That evidence is often gathered by hand before an audit, and it goes out of date as soon as the code changes.
Watchdog collects the part of that evidence that can be read from your code, at every survey and across every repository in your product. It checks libraries for known vulnerabilities, looks for passwords and keys left in the code, and checks how data is encrypted. It also checks whether the images and forms on your web pages carry the descriptions that screen readers need. It keeps a list of every library and licence your product contains (SBOM). For OWASP ASVS and ISO 27001, it also lists beside each requirement the problems found in your code that relate to it, so you know what to fix before you declare it.
Watchdog also writes the parts of the report it can work out from your surveys, such as how the evidence was gathered. A requirement Watchdog caught failing stays open until a survey shows it fixed, and nobody can tick it off by hand. A named person at your company declares the rest and signs the report, and every line says whether Watchdog checked it or a person declared it, so an auditor knows where each answer comes from.
Switch on any regulation or standard on any plan. Every declaration and every signature is made by a person at your company.
The work Watchdog does for you
Watchdog checks what a tool can check, and organises the rest for the person who declares it.
Every regulation and standard is a list of requirements. A check can find what is wrong in the code, but whether a requirement is met often also depends on how the product runs and how your company works. Watchdog therefore sorts every requirement into one of three kinds, and does as much of the work as each kind allows.
Checked by Watchdog
These requirements can be read from the code: libraries with known vulnerabilities, passwords and keys left in the code, how data is encrypted, and whether your web pages describe their images, label their form fields and use enough colour contrast. Watchdog checks them at every survey, across every repository in your product, and lists anything it finds with where it was found, so your team knows what to fix. A requirement counts as met only when the check comes back clean everywhere, and nobody can tick it off by hand.
Backed by Watchdog’s evidence
These depend on how the product runs as well as on its code, such as secure default settings, who can reach which pages, and backups. Watchdog backs each one with its checks of the code, and when it can start a copy of your product in its own sandbox, it adds what it saw there for the Cyber Resilience Act and NIS2, such as which network ports the product opens and which pages answer without a login. A person at your company confirms each one with that evidence in front of them.
Declared by a person
These are about how your company works, such as reporting an incident to the authorities within the deadline, planning resilience tests and deciding who is accountable for security. Watchdog lists them for a person at your company to declare, records each answer as that person’s declaration, and on a product’s report asks for every declaration to be renewed after twelve months, so none is left to go out of date.
Included in every plan
Watchdog covers NIS2, DORA, the Cyber Resilience Act, GDPR and the standards auditors and customers ask for.
The EU regulations apply to a product or to the company behind it, so you assess them for a whole product, however many repositories it spans. The standards for security, accessibility and the software supply chain can also be declared for a single repository, because one piece of software can meet them on its own.
Four of the regulations also set deadlines for reporting an incident to the authorities. Watchdog keeps each reporting duty as its own list next to the regulation it belongs to, because it applies only after something has gone wrong, and a person declares every requirement in it.
For a whole product
NIS2
The EU’s cybersecurity rules for essential and important companies, such as energy, transport, health and digital services. At every survey Watchdog checks the technical measures: known vulnerabilities in the libraries you use, passwords and keys left in the code, encryption, and the security settings of your servers and containers. It also collects evidence for backups and access control, and lists the security policies, staff training and incident handling for a person at your company to declare. The reporting duty in Article 23 has its own list: an early warning within 24 hours, a notification within 72 hours and a final report within a month.
For a whole product
DORA
The EU’s rules for the digital resilience of banks, insurers and other financial companies. At every survey Watchdog checks for known vulnerabilities and outdated libraries, secure coding, encryption and the configuration of your servers and containers, and it collects evidence for your list of systems and who can access them. It lists the risk framework, the resilience-testing programme and the oversight of IT suppliers for a person at your company to declare. The reporting duty in Article 19 has its own list: the initial, intermediate and final reports on a major incident, and what your clients must be told.
For a whole product
Cyber Resilience Act
The EU’s cybersecurity rules for products with digital elements, which apply from 11 December 2027. At every survey Watchdog checks that no library with a known vulnerability ships in your product and that data is encrypted, and it produces the list of components (SBOM) the regulation asks for. It also collects evidence for secure default settings, access control and your policy for receiving vulnerability reports. The reporting duty in Article 14 has applied since 11 September 2026: 24 hours, 72 hours and 14 days to report a vulnerability that attackers are using. Watchdog shows when a library in your product is on the list of such vulnerabilities kept by CISA, the US cybersecurity agency.
For a whole product
GDPR
The technical measures GDPR asks for in Articles 25 and 32: protecting personal data by design and keeping it secure. At every survey Watchdog checks encryption, passwords and keys left in the code, and known vulnerabilities, and it collects evidence for data minimisation, backups and who can reach personal data. The breach duty in Articles 33 and 34 has its own list: report a breach to the authority within 72 hours, and tell the people affected when the risk to them is high.
For a whole product
ISO 27001
The international standard for managing information security. At every survey Watchdog collects evidence for the technical controls in Annex A. It checks vulnerabilities, secure coding, passwords left in the code and encryption, and it collects evidence for backups, logging, configuration and access rights. Beside each control it lists the related problems found in your code. It helps you prepare for certification, which an accredited auditor grants.
For a whole product
OWASP DSOMM
A model for how mature a team’s security practice is, from automated security testing to training (DevSecOps Maturity Model). Watchdog lists every activity for a person at your company to assess. Where a problem found in your code shows that an activity isn’t practised yet, it shows that beside the activity, so the self-assessment starts from evidence.
Per repository or product
WCAG 2.2
The web accessibility standard, at level AA. At every survey Watchdog checks your web code for descriptions on images, labels on form fields, page structure, keyboard use and colour contrast, and lists the requirements that need a person’s judgement, such as whether error messages are clear. When a survey finds web pages in a repository, Watchdog switches WCAG on by itself and asks you once whether to keep it. A signed declaration produces an accessibility conformance report (ACR) for your customers and auditors.
Per repository or product
EN 301 549
The EU standard for accessible ICT, which the EU Accessibility Act and public-sector buyers rely on. For its web part, which follows WCAG 2.1 AA, Watchdog runs the same checks as for WCAG. It lists the other parts, such as hardware, documents and support services, for a person at your company to declare.
Per repository or product
OWASP ASVS
A checklist for verifying the security of web applications. At every survey Watchdog checks your code for protection against injection, encryption, security headers, configuration and the libraries you use. Beside each requirement it lists the related problems found in your code, so you know what to fix before you confirm it.
Per repository or product
OWASP SCVS
A standard for checking the outside components your software is built from. At every survey Watchdog checks that every component is known and has a fixed version, finds outdated and vulnerable components, and identifies each component’s licence. It also collects evidence on how your build pipeline records and signs what it produces.
Per repository or product
SSDF
The US framework for secure software development, which US government buyers ask suppliers to attest to. At every survey Watchdog checks secure coding, passwords left in the code, the libraries you reuse and their licences, and whether people have a way to report vulnerabilities to you. It also collects evidence on how your builds and security tests are set up.
Per repository or product
SLSA
A framework for showing how your software was built, so that a release can’t be changed unnoticed between your code and your users. Watchdog collects the evidence on whether your builds record how each release was made (provenance) and publish that record.
On a repository you can switch each standard on or off, or leave it on automatic. Every regulation and standard, the declarations and the signed report are included in every plan.
Built for an auditor’s questions
Watchdog won’t let you pass a requirement it caught failing.
Caught failures stay open
A requirement Watchdog checks counts as met only when a survey finds nothing wrong with it. When a survey finds a problem, the requirement stays open until a later survey shows it fixed, and nobody can tick it off by hand. The auditor sees exactly which requirements Watchdog proved and which are still being worked on.
Signed, sealed and traceable
A person at your company signs the report with their name and role, and Watchdog seals it with a fingerprint of its exact content (SHA-256) and its own digital signature, so any change made afterwards shows. Every line says whether Watchdog checked it or a person declared it, and the report names the version of the rules it was made against and comes in English and Danish. When a buyer’s acceptance criteria ask for a signed declaration, yours counts towards them automatically.
Your declaration, with the evidence behind it
Each of these regulations and standards asks your company to show that it meets them. Watchdog gives you the evidence to do that: what was checked at every survey, what a person at your company declared and when, and what is still open. Where a standard leads to a certificate, such as ISO 27001, the report is the material you bring to the auditor who grants it.
Checking a supplier’s software rather than your own? In Assay, our product for people who buy software, you set the requirements a supplier must meet, such as a minimum score and a signed declaration for the regulations you name, and Assay shows whether each repository meets them.
See the compliance evidence Watchdog collects for your own product. Your first survey is free, with nothing held back.
Sign in with GitHub, GitLab, Bitbucket or Azure DevOps · no card · every regulation and standard is included in every plan · the first survey of every repository you connect is free.
Next: The Cyber Resilience Act, and the evidence Watchdog gives you · From code host to your first baseline, or browse all the guides.
More about Watchdog: What you get · What we measure · Security and data · Where Watchdog fits with your tools.