NIS2
NIS2 checklist under Section 30 BSIG
Vulnerability management and effectiveness testing in the context of all measures.
A penetration test is an authorised, simulated attack: specialists use the same techniques as real attackers to find vulnerabilities before they are exploited. Süddeutsche Datenschutzgesellschaft mbH (SDG) carries out penetration tests of your web applications, APIs and cloud environments. You receive a report with all findings, their rating and specific recommendations, plus a debrief and, on request, a retest.
A pentest shows whether your security measures hold up in practice. This helps you with customers and your cyber insurer, and also when demonstrating the effectiveness of your measures under NIS2, ISO 27001 or KRITIS.
Login and session management, permissions, input validation, injection vulnerabilities and configuration, for example based on the OWASP Web Security Testing Guide.
Content management system and plug-ins, customer accounts and payment functions, forms, server and TLS configuration.
Authentication and authorisation, access to other users' records, rate limiting, error handling and data leaks.
Configuration of services and storage, identities and permissions, publicly accessible resources and logging.
We test networks and infrastructure primarily with automated vulnerability scans; manual infrastructure tests are carried out with cooperation partners. Our offering does not include tests of Active Directory, Wi-Fi, OT, ICS and IoT systems, hardware and firmware, mobile apps (we do test their APIs), social engineering, physical tests, or red teaming, purple teaming and TLPT.
All test steps are logged. Remediation itself is not part of the test; on request we support you with it separately.
Why SDG
For continuous monitoring between two tests, our security portal offers vulnerability analysis and real-time monitoring. On request, our external information security officer takes charge of managing your information security.
Knowledge
Read about the role security tests play in the regulations in our specialist articles.
NIS2
Vulnerability management and effectiveness testing in the context of all measures.
ISO 27001
The controls at a glance, including technical vulnerabilities and security testing.
KRITIS
How the BSI rates implementation levels and where penetration tests come in.
The risk is kept low by agreeing everything in advance: scope, time windows, excluded systems and emergency contacts are defined in writing, and we report critical findings immediately. Disruption can never be ruled out completely with active tests, which is why this coordination is so important.
Not as part of the test. The report contains specific recommendations for remediation. On request we support you with implementation as a separate service and check in a retest whether the vulnerabilities have been closed.
Yes. Cyber insurers ask about security measures in their risk questionnaire. The report is documented evidence that your internet-facing systems are tested regularly. Which evidence your insurer requires follows from the questionnaire and the policy terms. Check the exclusions there as well, as many cyber insurance policies exclude damage caused by war and state-sponsored cyber attacks.
That depends on the risk and how quickly your systems change. Regular tests, for example annually, have proved their worth, as have tests before new applications go live, after major changes and after security incidents.
That depends on the scope, i.e. the number and type of systems and the depth of testing. We do not quote flat rates. After the free initial consultation and agreement on the test scope, you receive a realistic estimate of the effort involved.