Germany

BSI NESAS Product Certification Scheme (NESAS-Produkte)

44 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

44 controls 0 frameworks share controls with it Germany verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1Aim and integration of the scheme0
2.1.1What BSI NESAS certifies and the legal basis0
3.1.1Applicant's duty to participate and to disclose vulnerabilities and incidents0
3.1.2The BSI audit team0
3.1.3Commission a recognised evaluation facility0
3.1.4The BSI certification body0
3.2.1Development and lifecycle processes that meet the NESAS security requirements0
3.2.2aAssign the network product to a valid audit and an evaluable product class0
3.2.2bThreat mitigation scope and the operational environment0
3.3.1The four phases of certification0
3.3.2.1Preparation phase tasks of the vendor0
3.3.2.3Application form, language and third-party declarations0
3.3.3.1Audit phase: scope, site, preparation and impartiality0
3.3.3.2Process documentation submitted to the lead auditor over the encrypted exchange platform0
3.3.3.3aCooperation during the audit: encryption, schedule, clarifications and resources0
3.3.3.3bAudit result, re-audit within three months and the audit report0
3.3.4.1Evaluation phase: SCAS selection, valid audit and impartiality0
3.3.4.2aDocument mitigation of every TR 33.926 threat0
3.3.4.2bEvidence package delivered to the evaluation facility0
3.3.4.2cSoftware bill of materials and vulnerability analysis0
3.3.4.2dArchitectural overview of the network product0
3.3.4.3aCooperation during the evaluation: schedule, kick-off, remote and external testing, corrections0
3.3.4.3bCorrected product versions during evaluation and the Impact Analysis Report0
3.3.5aCertification phase: draft report, hearing and objection0
3.3.5bArchive the evaluation evidence for the certificate's validity plus three years0
3.3.5cCosts, ancillary provisions and the code of symbols0
3.3.6Final documents0
4.1aConditions for including a minor update in an existing certificate0
4.1bApply for inclusion with an Impact Analysis Report and, where needed, a laboratory report0
4.2Recertification of a modified product and reuse of earlier test results0
5.1Basis for the certification0
5.2Confidentiality and encrypted document exchange0
5.3.2Evaluation contract and schedule discipline0
5.3.3Validity of criteria, interpretations and referenced documents0
5.3.4Reuse of evaluation results0
5.3.5Certification number0
5.4.1What the certificate covers and how its users must treat it0
5.4.2Time limits: two-year audit validity and two-year certificate validity0
5.5-5.6Costs and contact with the certification body0
6.1Publication of certificates and the consequence of withholding consent0
6.2Publication of ongoing procedures0
7References and glossary0
A.1-2Impact Analysis Report: identification, basis and description of changes0
A.3-4Impact Analysis Report: reuse of results and annexes0

Tell me when BSI NESAS Product Certification Scheme (NESAS-Produkte) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for BSI NESAS Product Certification Scheme (NESAS-Produkte), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition