BSI Grundschutz++ (GS++) — SP 800-53 Coverage
How well do NIST SP 800-53 Rev 5 controls address each BSI Grundschutz++ requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.
Clause-by-Clause Analysis
Sorted by clauseGC.1.1 Establishing and maintaining an ISMS Errichtung und Aufrechterhaltung eines ISMS
Rationale
PM-01 sets up an organisation-wide security programme plan, reviewed and updated, which is the nearest equivalent of a documented ISMS. PM-31 keeps the programme maintained through a continuous monitoring strategy with response actions.
Gaps
GS++ asks for an ISMS that follows the GS++ method through its plan-do-check-act cycle. Apply the method in full, using the programme plan and monitoring strategy as a base.
GC.1.2 Approval of the ISMS Freigabe des ISMS 70%
Rationale
Under PM-01, a senior official accountable for the risk approves the security programme plan and its management controls. That matches authorisation by top management at the level of the whole programme.
Gaps
GS++ asks top management to authorise each defined ISMS procedure. SP 800-53 has the programme plan approved as a whole, so have top management sign off each procedure too.
Mapped Controls
GC.2.1 Defining the organisation's external context Festlegung des externen Kontextes der Institution
Rationale
PM-16 runs a threat awareness programme that brings in the outside threat landscape through shared threat intelligence. PM-28 identifies and documents the assumptions and constraints that shape risk management, legal and regulatory ones included.
Gaps
GS++ asks for a systematic analysis of every external factor that bears on the ISMS, such as societal, economic, technological and environmental ones. Carry out that analysis and document it.
GC.2.2 Defining the organisation's internal context Festlegung des internen Kontextes der Institution
Rationale
PM-07 documents the existing IT infrastructure and information systems in an enterprise architecture built with security in mind. PM-11 defines the mission and business processes and the protection needs that follow from them. PM-28 records internal assumptions, constraints, priorities and risk tolerance.
Gaps
GS++ asks for an analysis of internal factors such as the organisation's strategy, values, structure and culture. Analyse these alongside the architecture and the business processes.
GC.3.1 Compliance management: procedures and rules Verfahren und Regelungen
Rationale
PM-01 gives an overview of the requirements the security programme must meet, compliance included. PM-28 documents the constraints on risk decisions, such as laws and contracts. PT-02 determines and documents the legal authority for processing personal data (GC.3.1.1). AT-03 trains the people responsible for their roles, which helps prevent breaches of obligations (GC.3.1.4).
Gaps
GS++ asks for a register of legal and contractual obligations, each with its priority, including an analysis of contracts (GC.3.1.3). Consult your legal and data protection functions as you build it (GC.3.1.2).
GC.4.1 Analysis of external interested parties Analyse der externen interessierten Parteien 25%
Rationale
PM-28 frames risk by documenting the constraints and priorities behind risk decisions. Those include what outside parties, such as regulators and customers, expect of the organisation.
Gaps
GS++ asks you to identify each external interested party, such as regulators, customers, service providers and the public, and their expectations. Then decide which of those expectations become binding obligations for the ISMS.
Mapped Controls
GC.4.2 Analysis of internal interested parties Analyse der internen interessierten Parteien
Rationale
PM-11 derives protection needs from mission and business needs that the organisation's own stakeholders define. PM-28 frames risk in consultation with stakeholders across the organisation and records their priorities and risk tolerance.
Gaps
GS++ asks you to identify each internal interested party and their expectations of the ISMS. Examples are management, the security officer, staff and the works council. Document that analysis.
GC.5.1 Setting information security objectives Festlegung von Zielen für die Informationssicherheit
Rationale
PM-06 develops outcome-based measures of performance, which make security goals measurable. PM-09 sets the organisation's overall risk management strategy (GC.5.1.1). PM-01 states management commitment and roles in a programme plan that a senior official approves. That plan serves as the security policy and its approval (GC.5.1.2 to GC.5.1.4). The policy controls of the other families, such as AC-01 and IR-01, supply the policy for each topic, under OSA's rule for policy clauses, which follows NIST's crosswalks.
Gaps
GS++ asks for concrete, measurable security objectives drawn from the organisation's context. It also asks for a single security policy that top management authorises. Write both, with the programme plan and measures as a base.
GC.6.1 Defining the scope of the ISMS Festlegung des Geltungsbereichs 50%
Rationale
PL-02 has a security plan define each system's components and operating environment, which sets the system's boundary. The authorising official approves the plan before the system goes into use.
Gaps
GS++ asks for one scope for the whole ISMS, naming the units and sites it covers and the areas it leaves out. Define it at organisation level, with the system boundaries inside it.
Mapped Controls
GC.7.1 Procedure for information security classification Vorgehen bei der Informationssicherheitseinstufung
Rationale
PM-11 defines the mission and business processes and the information protection needs that arise from them (GC.7.1.1). RA-02 categorises systems and the information they handle by impact, and the authorising official approves the result (GC.7.1.2).
Gaps
GS++ classifies protection needs on two levels, normal and high, for each business process. SP 800-53 categorises systems and information types by impact, so apply the two levels to your processes as well.
GC.7.2 Business processes with high protection needs Geschäftsprozesse mit hohem Schutzbedarf 80%
Rationale
RA-03 assesses the likelihood and impact of threats to a system and the information it handles. That gives the dedicated risk analysis the requirement asks for on processes and information with high protection needs.
Gaps
GS++ makes a high protection need the trigger for a dedicated risk analysis. SP 800-53 asks for a risk assessment of every system, so flag the processes with high needs and give each its own analysis.
Mapped Controls
GC.8.1 Procedure for ISMS resource planning Verfahren zur Ressourcenplanung
Rationale
PM-03 includes the resources the security programme needs in capital planning and makes them available. SA-02 determines and allocates the resources needed to protect each system.
Gaps
GS++ asks for continuous, cost-effective planning of ISMS resources. Include staff and technical resources in that planning, alongside the budget.
GC.9.1 Setting up a security organisation Festlegung einer Sicherheitsorganisation
Rationale
PM-01 identifies and assigns roles and responsibilities in the programme plan (GC.9.1.1). PM-02 appoints a senior information security officer with the mission and resources to run the programme (GC.9.1.1.1). PM-29 appoints a senior accountable official for risk and sets up a risk executive function as a governing body. PM-13 defines the skills each security role needs (GC.9.1.1.4). AC-05 separates duties to avoid conflicts of interest (GC.9.1.1.3).
Gaps
GS++ asks for an independent security officer who reports directly to top management and has a right of direct access to them (GC.9.1.1.1, GC.9.1.1.1.2). It also asks for a deputy for every relevant ISMS role (GC.9.1.1.2).
GC.10.1 Defining a procedure for communication management Festlegung eines Verfahrens zum Kommunikationsmanagement
Rationale
PM-01 reflects in the programme plan the coordination among the internal entities responsible for security. PM-15 sets up standing contact with security groups and associations for external exchange (GC.10.1.1). SA-03 builds security roles and risk management into the system life cycle, so security staff take part in projects at defined stages (GC.10.1.2).
Gaps
GS++ asks for one procedure that sets who communicates what, when, with whom and how, inside the organisation and outside it. Include the supervisory authorities and your contacts there.
GC.11.1 Document control Dokumentenlenkung
Rationale
PM-01 has the programme plan reviewed and updated, and protects it from unauthorised disclosure and change. SI-12 manages and retains information, policies and plans included, in line with laws and operational requirements.
Gaps
GS++ asks for control of each ISMS document across its whole life, with metadata, versioning, release and withdrawal. Set up one document control process for all ISMS documents.
GC.12.1 Governance: risk management method Methodik für das Risikomanagement
Rationale
PM-09 sets an organisation-wide risk management strategy, with accepted assessment methods, and applies it consistently. PM-28 frames risk with assumptions, constraints, priorities and risk tolerance drawn from the organisation's context. RA-01 puts the method in writing as risk assessment policy and procedures.
Gaps
GS++ asks the method to take in the business process analysis and the interested parties as well as the context. Name both as inputs to your method.
STM.1.1 Defining and bounding the information domain Definition und Abgrenzung des Informationsverbunds
Rationale
PL-02 has a security plan define each system's components, business context, environment and connections, which together set its boundary. PM-05 keeps an inventory of the organisation's systems, which supports a traceable decision on which systems are in scope.
Gaps
GS++ draws the information domain around people, sites, buildings and outsourced parts as well as systems. SP 800-53 draws a boundary around each system, so add the other elements yourself.
STM.1.2 Documenting external interfaces Dokumentation der externen Schnittstellen
Rationale
CA-03 documents the interface characteristics and security requirements of each information exchange. PL-02 describes the system's dependencies on and connections to other systems. SA-09 assigns oversight and responsibilities for external system services, the organisational interface to outsourced processes.
Gaps
GS++ asks for every interface to external processes, organisational and infrastructural ones included. SP 800-53 covers the interfaces between systems and services, so document the other kinds alongside them.
STM.2.1 Creating a requirement package Erstellung eines Anforderungspakets
Rationale
PL-10 selects a control baseline for the system, the counterpart of building a requirement package. PL-11 tailors that baseline, scoping controls in or out with a reason and adding new ones (STM.2.1.5 to STM.2.1.7). PL-02 records the selected controls and the reason for each tailoring decision. CM-08 captures the assets the requirements apply to (STM.2.1.2).
Gaps
GS++ assigns each asset to target object categories and models their requirements onto it (STM.2.1.3, STM.2.1.4). Categories pass down the asset hierarchy, and a consolidation check ends the step. Follow the GS++ method for these steps.
STM.3.1 Reviewing the assigned security level Überprüfung des gesetzten Sicherheitsniveaus
Rationale
PL-10 selects a control baseline by impact level, which sets the initial level of protection. PL-11 tailors the baseline to the organisation's own conditions, the counterpart of revisiting the security level when the context changes.
Gaps
GS++ sets a security level for each requirement, either normal (state of the art) or elevated. SP 800-53 sets protection through baselines and enhancements, so review each requirement's level when the context changes.
STM.4.1 Carrying out the risk analysis Durchführung der Risikobetrachtung 70%
Rationale
RA-03 has the organisation conduct and document a risk assessment and update it when conditions change. That delivers the risk analysis the GS++ method calls for, such as for high protection needs or requirements left unimplemented.
Gaps
GS++ sets the triggers for a risk analysis. They are a high protection need, a lowered security level, an unimplemented requirement and an asset GS++ leaves uncovered. SP 800-53 asks for a risk assessment of every system, so watch for these triggers yourself.
Mapped Controls
STM.5.1 Setting requirement parameters Setzen von Parametern
Rationale
PL-11 includes assigning values to organisation-defined control parameters as part of tailoring, which is what setting GS++ parameters does. PL-02 records in the security plan how each control is implemented, including the values chosen.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
UMS.1.1 Determining the implementation status Ermittlung des Umsetzungsstatus
Rationale
CA-02 assesses controls at a set frequency to find whether they are implemented correctly. CA-07 adds ongoing control assessments as part of continuous monitoring. PL-02 records which controls are in place and which are planned.
Gaps
GS++ gives each requirement a yes or no status. A requirement counts as implemented once every requirement it depends on is implemented too, so apply that rule when you record status.
UMS.1.2 Assessing the residual risk Bewertung des Restrisikos
Rationale
RA-03 determines the likelihood and impact of harm, including harm from controls still missing, which gives the residual risk. RA-07 decides how to treat findings in line with risk tolerance, including whether to accept the risk. CA-06 has the authorising official accept the residual risk before operation.
Gaps
GS++ suggests consolidating the residual risk from requirements left unimplemented, so top management can follow it. Prepare that summary for top management.
UMS.2.1 Implementation planning Umsetzungsplanung
Rationale
CA-05 documents the planned remediation of weaknesses and missing controls in a plan of action and milestones. PM-04 runs an organisation-wide process that keeps those plans developed and maintained.
Gaps
GS++ asks you to look for measures that meet several requirements at once. Build that search into your implementation planning.
UMS.2.2 Implementation planning: prioritising measures Priorisierung von Maßnahmen
Rationale
PM-04 reviews plans of action against the risk management strategy and organisation-wide priorities for risk response. RA-07 responds to findings in line with the organisation's risk tolerance, which gives a risk-based order.
Gaps
GS++ asks you to rank measures by their dependencies and the resources available as well as by risk. Add both criteria to your prioritisation.
UMS.3.1 Naming those responsible for implementation Benennung von Umsetzungszuständigen 40%
Rationale
CA-05 documents each planned remediation action in a plan of action and milestones. That plan is the usual place to name the owner of each action.
Gaps
GS++ asks you to name a person or team responsible for each requirement still open. Add an owner to every action in your plan of action and milestones.
Mapped Controls
UMS.4.1 Setting implementation deadlines Festlegung von Umsetzungsfristen
Rationale
CA-05 sets milestones in the plan of action, which give target dates for each remediation action. PM-04 keeps those plans and their milestones maintained and reported across the organisation.
Gaps
GS++ asks for a realistic target date for each measure. Track those dates and act when one is missed.
UMS.5.1 Authorising exceptions Autorisierung von Ausnahmen
Rationale
Under CA-06, a senior official accepts risk when authorising a system, which covers approving deviations. RA-07 allows risk to be accepted, with a justification, in line with the organisation's risk tolerance.
Gaps
GS++ asks for a general exception process for any obligation, with a named person or role who approves each exception. Set that process up alongside system authorisation.
UMS.5.2 Documenting exceptions Dokumentation von Ausnahmen 55%
Rationale
PL-02 has the security plan record the reason for each tailoring decision. That documents why a control is scoped out or adjusted, which covers exceptions to the control baseline.
Gaps
GS++ asks you to document every approved exception with its reason, for any obligation. A ticket system or configuration database can hold that record.
Mapped Controls
UMS.6.1 Tracking implementation progress Nachverfolgung des Umsetzungsfortschritts
Rationale
CA-05 updates the plan of action and milestones from assessment and monitoring findings as remediation proceeds. PM-04 runs a process that keeps those plans maintained and reported, which tracks progress across the organisation.
Gaps
GS++ recommends tracking progress with key performance indicators. Define indicators for the implementation plan and report against them.
UMS.6.2 Updating the implementation plan Fortschreibung des Umsetzungsplans
Rationale
CA-05 updates the plan of action and milestones at a set frequency, using findings from assessments, audits and monitoring. PM-04 keeps those plans maintained as an ongoing, organisation-wide process.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
UMS.7.1 Maintaining compliance during implementation Wahrung von Compliance in der Umsetzung
Rationale
CA-02 checks that controls meet the established security and privacy requirements, which include legal ones. CA-07 keeps assessing controls while measures go in, and CA-07(04) adds compliance monitoring.
Gaps
GS++ asks for a procedure that checks compliance with legal and contractual obligations while measures are put in place. Add those obligations to your checks, for example with checklists or audits.
VRB.1.1 Procedure for continuous improvement Verfahren zur kontinuierlichen Verbesserung
Rationale
PM-01 reviews and updates the programme plan at a set frequency and after defined events. PM-31 sets response actions to the results of monitoring and assessment. PM-04 turns the resulting findings into actions that plans of action track to completion.
Gaps
GS++ asks for a procedure to improve the ISMS as a whole, on a continuing basis. Build that procedure on top of the plan reviews and monitoring.
VRB.2.1 Handling nonconformities Umgang mit Nicht-Konformitäten
Rationale
CA-05 records each weakness found in assessments and audits, with its planned correction. CA-07 correlates and analyses monitoring results, and its trend analyses (CA-07(03)) can show recurring problems. IR-04 feeds lessons learned from incidents back into procedures to prevent recurrence.
Gaps
GS++ asks for a method that finds the root cause of each nonconformity and checks whether it could recur. Apply it to every nonconformity, whatever its source.
VRB.2.2 Adapting the ISMS after nonconformities Anpassung des ISMS 50%
Rationale
PM-01 reviews and updates the security programme plan after defined events, such as audit findings or recurring nonconformities. Each of those updates is a point at which to adapt the programme.
Gaps
GS++ asks you to review regularly whether nonconformities point to systemic weaknesses that call for changes to the ISMS. Add that question to each review of the programme plan.
Mapped Controls
VRB.3.1 Identifying opportunities for improvement Identifikation von Verbesserungspotenzialen 30%
Rationale
PM-31 correlates and analyses assessment and monitoring information as part of the continuous monitoring strategy. That analysis, with its response actions, can bring opportunities for improvement to light.
Gaps
GS++ asks for a method that looks for improvement opportunities proactively, ahead of any problem, and weighs the pros and cons of each. Set up that method alongside the monitoring.
Mapped Controls
VRB.4.1 Corrective measures Korrekturmaßnahmen
Rationale
CA-05 sets out the remediation that corrects weaknesses and deficiencies in a plan of action and milestones. RA-07 responds to the findings in line with the organisation's risk tolerance.
Gaps
GS++ asks for corrective measures that remove the root cause of each fault as well as its symptoms. Trace each finding to its root cause before you plan the fix.
VRB.4.2 Improvement measures Verbesserungsmaßnahmen
Rationale
PM-04 documents and prioritises actions in plans of action and milestones, where improvement measures can be tracked. PM-31 sets response actions that follow from the analysis of monitoring and assessment results.
Gaps
GS++ asks for proactive measures that take up improvement opportunities, chosen by weighing their pros and cons. Plan these alongside the remediation of weaknesses.
VRB.5.1 Improvement plan: prioritising measures Priorisierung von Maßnahmen
Rationale
CA-05 schedules corrective actions in a plan of action with milestones. PM-04 reviews those plans against the organisation-wide priorities for risk response actions, which sets their order.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
VRB.6.1 Reviewing the improvement achieved Überprüfung der erreichten Verbesserung
Rationale
CA-02 assesses whether controls operate as intended and produce the desired outcome. CA-07 keeps checking their effectiveness over time through ongoing assessments at set frequencies.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
VRB.6.2 Evaluating the improvement achieved Bewertung der erreichten Verbesserung
Rationale
PM-06 develops measures of performance that compare effectiveness before and after a change. CA-07 monitors over time, and its trend analyses (CA-07(03)) show whether the security level is improving. PM-31 analyses organisation-wide metrics to show the trend.
Gaps
GS++ asks you to weigh the pros and cons of the improvement achieved. Add that weighing to each evaluation.
VRB.7.1 Handling compliance violations Behandlung von Compliance-Verstößen
Rationale
IR-06 has staff report suspected incidents, policy violations included, within a set time. IR-04 investigates and handles them, with documented follow-up. IR-08(01) adds a process to assess harm to affected individuals and decide whether to notify them of a breach. PS-08 sets a formal sanctions process for people who break security policies.
Gaps
GS++ asks for a procedure that defines and categorises compliance violations, legal and contractual ones included, and respects the rights of the people affected. Extend incident handling to cover them.
PERF.1.1 ISMS performance evaluation: procedures and rules Verfahren und Regelungen
Rationale
CA-01 sets the policy and procedures for assessment, authorisation and monitoring, which are the rules for measuring and evaluating. PM-06 tracks and reports measures of performance. PM-31 sets organisation-wide metrics, monitoring frequencies, analysis and reporting.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERF.1.2 Evaluating the implementation plan Evaluation des Umsetzungsplans
Rationale
CA-05 updates the plan of action and milestones at a set frequency from assessment and monitoring results. PM-04 reviews those plans against the risk management strategy and priorities, and reports on them.
Gaps
GS++ asks the review to check that each measure meets its deadline and is correct in content. Add both checks to your regular review of the plan.
PERF.1.3 Keeping the requirements up to date Aktualität der Anforderungen
Rationale
PL-02 reviews the security plans, with their requirements and controls, at a set frequency and updates them when the system or its environment changes. RA-03 updates the risk assessment on significant changes, such as new threats.
Gaps
GS++ asks you to recheck the modelling of the requirement package regularly, usually once a year. Follow the GS++ method for that check.
PERF.2.1 Reviewing compliance with obligations Überprüfung der Einhaltung von Verpflichtungen
Rationale
CA-02 assesses controls against the established security requirements at a set frequency. CA-07 adds ongoing monitoring, including checks after changes, and CA-07(04) adds compliance monitoring.
Gaps
GS++ asks for regular and event-driven checks against your documented legal and contractual obligations. Add those obligations to the scope of your assessments.
PERF.3.1 Building and maintaining an audit programme Aufbau und Pflege eines Auditprogramms
Rationale
CA-01 sets the assessment policy and procedures behind the audit process. CA-02 selects assessors, plans each assessment's scope and procedures and runs it at a set frequency (PERF.3.1.1, PERF.3.1.4). CA-02(01) adds independent assessors (PERF.3.1.3). PM-14 keeps testing and monitoring plans reviewed against the risk strategy, which makes the programme risk-based (PERF.3.1.2).
Gaps
GS++ asks you to build and maintain one or more audit programmes. Manage each programme as a whole, in the way ISO 19011 describes, over and above single assessments.
PERF.3.2 Documenting audit results Dokumentation von Auditergebnissen 65%
Rationale
CA-02 produces a report for each assessment, which serves as the audit report. It also gives the results to defined individuals or roles, the stakeholders who need them (PERF.3.2.2).
Gaps
GS++ asks for one rating scheme for all audit findings (PERF.3.2.1). Define the scheme and use it in every assessment report.
Mapped Controls
PERF.4.1 Suitability review of the ISMS Eignungsprüfung
Rationale
PM-04 reports on plans of action, which gives the status of follow-up actions and the implementation plan (PERF.4.1.1, PERF.4.1.7). PM-06 reports the results of measures of performance. PM-31 reports security status to defined personnel at a set frequency. PM-26 collects complaints and feedback from individuals about security practices (PERF.4.1.6).
Gaps
GS++ asks for a management report on the suitability, adequacy and effectiveness of the ISMS. Include changed conditions and prioritised proposals with realistic effort estimates (PERF.4.1.2, PERF.4.1.9).
PERF.4.2 Report to top management Bericht an die Institutionsleitung
Rationale
PM-06 reports the results of measures of performance. PM-31 reports security and privacy status to defined personnel at a set frequency, which can include top management.
Gaps
GS++ names top management as the recipient. SP 800-53 lets you choose the recipients, so name top management among them.
PERF.5.1 Monitoring methods and tools Methoden und Tools
Rationale
PM-31 sets an organisation-wide continuous monitoring strategy. CA-07 carries it out for each system with set metrics and frequencies, and CA-07(06) adds automation. SI-04 deploys monitoring tools that detect attacks and unauthorised use. RA-05 scans for vulnerabilities at a set frequency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
RISK.1.1 Risk management: methods to a recognised standard Methodik für das Risikomanagement
Rationale
PM-09 sets an organisation-wide risk management strategy, with accepted methods, and applies it consistently. PM-28 frames the context the methods use, such as assumptions, constraints, priorities and risk tolerance. RA-01 puts the methods in writing as risk assessment policy and procedures.
Gaps
GS++ asks for methods that follow a recognised standard, such as ISO 27005, ISO 31000, BSI Standard 200-3 or NIST SP 800-30. Record the standard you chose.
RISK.1.3 Risk owner Risikoeigentümer
Rationale
CA-06 makes a senior official the authorising official, who is accountable for a system and accepts its risk. PM-10 designates individuals for defined roles in the risk management process. PM-29 appoints a senior accountable official for risk management and sets up a risk executive function.
Gaps
GS++ asks for an owner for each risk, with the authority to decide how it's treated. SP 800-53 assigns risk acceptance per system, so name an owner for every risk you record.
RISK.1.5 Approval of risk management Freigabe des Risikomanagements
Rationale
Under PM-01, a senior official accountable for risk approves the programme plan, which describes the risk management roles. PM-09 sets the organisation-wide risk management strategy and its methods. PM-28 documents and distributes the risk tolerance and criteria. PM-29 puts a senior accountable official in charge of risk management.
Gaps
GS++ asks top management to authorise the risk management procedures, role definitions and criteria themselves. Have top management sign them off and keep a record of the approval.
RISK.1.10 Approval of implementation planning Freigabe der Umsetzungsplanung
Rationale
CA-05 sets out the plan of action and milestones, the implementation plan for remediation, which forms part of the authorisation package. CA-06 has the authorising official accept the residual risk and authorise operation on that basis.
Gaps
GS++ asks each risk owner to authorise the implementation plan. Get that sign-off from the risk owners as well as from the authorising official.
ASST.1.1 Information and assets: procedures and rules Verfahren und Regelungen
Rationale
CM-01 sets configuration management policy and procedures, which govern the component inventory. MA-01 does the same for maintenance, and MP-01 for media protection, covering marking, storage, transport and sanitisation. Each documents its policy, gives it to the roles that need it and names an official to manage it (ASST.1.1.1 to ASST.1.1.3). SI-12 manages and retains information through its life cycle, in line with laws and policies.
Gaps
GS++ asks for one set of procedures and rules for information and related assets across their whole life cycle. SP 800-53 spreads this over several control families, so draw their policies together under one process.
ASST.1.2 Information and assets: regular review Regelmäßige Überprüfung
Rationale
CM-01, MA-01 and MP-01 review and update the configuration management, maintenance and media protection policies and procedures. Each does so at a set frequency and after events the organisation defines.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.2.1 Inventory of information Inventar der Informationen
Rationale
CM-08 keeps an inventory of system components, and CM-08(04) names the people responsible for them (ASST.2.1.1). CM-12 documents where the organisation processes and stores defined information, and who has access to it. PM-05 keeps an inventory of organisational systems, and PM-05(01) adds one for systems that process personal data.
Gaps
GS++ asks for an inventory of the categories of information the organisation holds, such as customer names and bank details. It also asks for a person or role responsible for each category. Add both to your inventory.
ASST.2.2 Inventory of systems Inventar der Systeme
Rationale
CM-08 keeps an inventory of system components with details such as an identifier, and CM-08(08) tracks their location. CM-08(03) detects unauthorised components (ASST.2.2.1). PM-05 keeps the inventory of organisational systems up to date. SI-04 detects unauthorised local, network and remote connections (ASST.2.2.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.2.3 Inventory of applications Inventar der Anwendungen
Rationale
CM-08 lists software components with details such as version, and CM-08(02) keeps the list current by automated means (ASST.2.3.2.1). CM-10 tracks licences and licensed use. CM-07(05) lets only authorised software run, and CM-11 governs what users may install (ASST.2.3.1). SR-04 documents the provenance of components and their data, the job a software bill of materials (SBOM) does (ASST.2.3.2).
Gaps
GS++ asks for an SBOM for each application. SR-04 records provenance, which covers part of that, so produce the SBOM itself and keep it with the inventory.
ASST.2.4 Data classification Klassifizierung 80%
Rationale
RA-02 categorises the system and the information it processes, stores and transmits by impact level. The impact level states how much protection that information needs.
Gaps
GS++ asks the organisation to put each set of data into a protection class, such as public, internal or confidential. RA-02 works at the level of systems and information types, so set up a classification scheme for the data itself.
Mapped Controls
ASST.3.1 Usage agreements for information and assets Nutzungsvereinbarungen
Rationale
PL-04 sets rules of behaviour for using information and systems, and users acknowledge them before they get access. PS-06 has users sign access agreements, such as acceptable use and non-disclosure agreements, before access. AC-21 helps users decide whether a sharing partner may receive information, so they share it on a need-to-know basis (ASST.3.1.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.3.2 Removal of unneeded residual data and metadata Entfernung nicht erforderlicher Rest- oder Zusatzdaten
Rationale
AC-04(25) sanitises data as it passes between security domains, to stop sensitive information spilling across. SI-12(01) limits the personal data elements the organisation processes to those it needs.
Gaps
GS++ asks the organisation to remove unneeded residual data and metadata, such as author names or location, from all its information. Set that up yourself, for example with automated filters and a manual check.
ASST.3.3 Labelling of information Kennzeichnung
Rationale
AC-16 attaches security attributes to information in storage, processing and transmission, and AC-16(05) shows them in readable form on output. MP-03 marks system media with distribution limits and handling caveats. PE-22 marks hardware components with the impact level of the information they may process.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.3.4 Labels on IT systems free of confidential data Kennzeichnung ohne vertrauliche Daten 30%
Rationale
SC-38 uses operations security to protect information an adversary could exploit, such as user identities. That extends to the details a label on an IT system shows.
Gaps
GS++ asks for labels on IT systems to leave out confidential details, such as the assigned staff member, site, network structure or department. Check physical labels and device names against that rule.
Mapped Controls
ASST.3.5 Tainting of data Tainting 90%
Rationale
SI-20 embeds data or capabilities in systems to detect the exfiltration of organisational data. That is the tainting GS++ describes, which makes data recognisable when it turns up elsewhere.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ASST.3.6 Verification of information against other sources Verifikation
Rationale
SI-22 identifies alternative sources of information and uses them when the primary source is corrupted. AU-06(03) and (05) correlate audit records across repositories and with other sources, which checks security events against further information.
Gaps
GS++ asks for a check of important information against a second, independent source, which helps spot false alarms. Choose the information that needs it and set up the check.
ASST.3.7 Pseudonymisation before sharing Pseudonymisierung 65%
Rationale
SI-19 de-identifies datasets by removing or replacing the elements that identify people. SI-19(04) masks, encrypts, hashes or replaces direct identifiers, which is what pseudonymisation does.
Gaps
SI-19 covers personal data. GS++ also asks for pseudonymisation of other information before the organisation shares it, such as internal IP ranges. Apply the same methods to that information.
Mapped Controls
ASST.3.8 Anonymisation before sharing Anonymisierung 70%
Rationale
SI-19 de-identifies datasets by removing the elements that identify people. SI-19(05) and (06) add statistical disclosure control and differential privacy, which make it hard to trace data back to a person.
Gaps
SI-19 covers personal data. GS++ also asks for anonymisation of other information before the organisation shares it, such as system configurations or account details. Apply the same methods there.
Mapped Controls
ASST.3.9 Keeping data up to date Aktualisierung
Rationale
SI-18 checks personal data for accuracy and timeliness and corrects or deletes outdated records. SI-21 refreshes defined information at set frequencies or generates it on demand.
Gaps
GS++ asks the organisation to keep all its data up to date, for example by comparing it with its sources. SI-18 does this for personal data. SI-21 refreshes information to limit exposure, so add an accuracy check for other data.
ASST.3.10 Authorisation of data locations Autorisierung von Datenlokationen
Rationale
CM-12 documents where the organisation processes and stores defined information, and records changes of location. SA-09(05) restricts processing and storage by external services to defined locations. PE-17 sets and documents the alternate work sites staff may use, such as mobile working.
Gaps
GS++ asks for a named person or role to authorise the permitted locations for each category of data. Assign that approval yourself, and record it with the locations these controls document.
ASST.3.11 Authorisation of systems that process data Autorisierung von Systemen
Rationale
CA-06 has a senior official authorise each system to operate, and so to process its information. AC-19 authorises mobile devices to connect, and AC-20 sets terms for external systems, with AC-20(03) restricting privately owned devices. CM-07(09) allows only authorised hardware, and MP-07 restricts types of media such as USB drives (ASST.3.11.1).
Gaps
GS++ asks the organisation to set, for each category of data, which systems and peripherals may process it. Draw up a list of permitted systems for each category, for example keeping highly confidential data on desktop devices.
ASST.3.12 Authorisation of people or organisations to access data Autorisierung von Personen oder Institutionen
Rationale
AC-02 approves accounts and authorises access on the basis of a valid authorisation and intended use. AC-03 enforces the approved authorisations for logical access. AC-06 grants each user only the access their assigned tasks need.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.3.13 Storage of physical assets Lagerung physischer Assets 45%
Rationale
MP-04 physically controls system media and stores them securely within controlled areas. That covers the media among the physical assets administrators keep in store.
Gaps
MP-04 covers media. GS++ asks administrators to keep all unissued physical assets, such as spare devices, in a designated store, for example a locked room or cabinet. Extend the storage rules to those assets.
Mapped Controls
ASST.3.14 Reserve of physical assets Reserve physischer Assets 55%
Rationale
MA-06 obtains maintenance support or spare parts within a set time of a failure. A reserve of spare devices is one way to meet that time.
Gaps
GS++ asks for a reserve of spare devices that covers expected demand until the next order arrives and goes into service. Size it from past demand, adjusted for changes such as a growing number of users.
Mapped Controls
ASST.3.15 Loan pool of physical assets Ausleihe physischer Assets 45%
Rationale
CM-02(07) issues specially configured devices to staff who travel to locations the organisation sees as high risk. Those devices act as a loan pool for that kind of trip.
Gaps
GS++ asks for enough loan devices to cover other occasions too, such as events or security incidents. Size the pool from a forecast of demand and keep it beyond the travel case.
Mapped Controls
ASST.4.1 Authorisation of interfaces for information exchange Autorisierung von Schnittstellen
Rationale
CA-03 approves and manages the exchange of information with other systems through agreements. CA-09 authorises and documents internal system connections. These cover technical interfaces, such as an API or encrypted cloud storage.
Gaps
GS++ also counts physical channels as interfaces, such as post or regular meetings in a protected place. Have a named person or role authorise those channels too.
ASST.4.2 Confidentiality and integrity in transport Vertraulichkeit und Integrität beim Transport
Rationale
SC-08 protects the confidentiality and integrity of information in transmission, and SC-08(01) uses cryptography to do it. MP-05 protects and controls media during transport outside controlled areas and keeps them accounted for.
Gaps
GS++ also covers the physical transport of whole systems. MP-05 protects the media inside them, so add measures for the device itself, such as tamper-evident packaging or keeping it on your person.
ASST.4.3 Authorisation of publications Autorisierung von Veröffentlichungen 75%
Rationale
AC-22 designates who may post information on publicly accessible systems. It reviews the content for nonpublic information before it goes up.
Gaps
AC-22 covers publicly accessible systems. GS++ asks a named person or role to approve every publication, such as press releases and research papers. Apply the same approval to those channels.
Mapped Controls
ASST.4.4 Proof of receipt Nachweis des Zugangs 80%
Rationale
AU-10 provides evidence that a recipient received a message, for example through digital message receipts. The sender can then show the message arrived if this is ever disputed.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ASST.4.5 Agreements on information exchange Vereinbarungen zum Austausch 70%
Rationale
CA-03 approves and manages information exchange through agreements, such as interconnection or non-disclosure agreements. Each agreement documents the security requirements for the information exchanged.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ASST.5.1 Documenting maintenance needs Wartungsbedarf dokumentieren
Rationale
MA-02 schedules and documents maintenance in line with manufacturer specifications and organisational requirements. MA-06 defines the components that need timely maintenance, and MA-06(01) sets intervals for preventive maintenance.
Gaps
GS++ also asks for documented maintenance needs for the infrastructure that systems depend on, such as power and cooling. Record those needs alongside the system components.
ASST.5.2 Managed maintenance Geregelte Wartungen
Rationale
MA-02 schedules and performs maintenance in line with manufacturer specifications. MA-06(01) adds preventive maintenance at set intervals, and MA-06(02) adds predictive maintenance.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.5.3 Authorisation of maintenance Autorisierung von Wartungen
ASST.5.4 Handling maintenance as changes and tests Behandlung als Änderungen und Tests
ASST.5.5 Maintenance windows Wartungsfenster 15%
Rationale
MA-02 schedules maintenance in advance. With a schedule in place, the organisation can tell users ahead of time when systems will be unavailable.
Gaps
GS++ asks the organisation to tell users in advance how long a maintenance outage will last and what it affects, such as applications or networks. Send that notice before each maintenance window.
Mapped Controls
ASST.5.6 Maintenance by external parties Wartung durch Externe 95%
Rationale
MA-05 has authorised staff with the needed skills supervise maintenance personnel who lack the required access authorisations. MA-05(01) adds escorts for them, which covers unvetted external technicians.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ASST.5.7 Documentation of maintenance Dokumentation von Wartungen
Rationale
MA-02 keeps maintenance records with content the organisation defines, such as the date, the components, the people involved and the work done. MA-04 keeps records of remote (nonlocal) maintenance too.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.6.1 Loss of assets Abhandenkommen
Rationale
IR-06 has staff report suspected incidents, such as a lost or stolen device. IR-04 handles the loss as an incident, with containment and recovery. MP-06(08) purges or wipes information remotely from a lost device.
Gaps
GS++ asks for a set procedure for lost or stolen assets that names each step and who is responsible for it. Write that procedure yourself, building on the incident handling these controls describe.
ASST.6.2 Return of lost assets Rückkehr abhandengekommener Assets
Rationale
SR-10 inspects systems or components for tampering, for example when they have been outside the organisation's control. SI-07 verifies the integrity of software, firmware and information, which detects unauthorised changes before the device goes back into use.
Gaps
GS++ asks for a set procedure for assets that come back after going missing, to check them before they return to use. Write that procedure yourself, using these inspections as its checks.
ASST.6.3 Conformity check on return of assets Konformitätsprüfung
Rationale
SR-10 inspects returned systems or components for physical and logical tampering. CM-02(07) applies defined controls to devices when their users return from travel.
Gaps
GS++ asks for one check on return that the asset still meets its requirements, for example an untampered device that still gets security updates. Combine these controls into that single check.
ASST.6.4 Reset to initial state on return Zurücksetzen auf Ausgangszustand
Rationale
CM-02 restores the system to its documented baseline configuration, which gives the defined starting state. MP-06 sanitises media before reuse, for example by clearing, purging or cryptographic erase, which deletes data left over from use.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.7.1 Uninstalling unneeded applications Nicht mehr benötigte Anwendungen 80%
Rationale
CM-07 configures systems to provide only the capabilities they need. CM-07(01) reviews systems at a set frequency and removes unnecessary software and services.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ASST.7.2 Retention and deletion periods Aufbewahrungs- und Löschfristen
Rationale
SI-12 retains information in line with laws, regulations and operational requirements, including long-term archiving (ASST.7.2.1). AU-11 retains audit records for a period that matches the retention policy.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.7.3 Managed deletion or destruction Geregeltes Löschen oder Vernichten
Rationale
SI-12(03) disposes of, destroys or erases information when its retention period ends. MP-06 sanitises media before disposal, release or reuse, with a strength that matches the classification (ASST.7.3.1, ASST.7.3.2). SR-12 disposes of components with defined techniques.
Gaps
GS++ asks for destruction to a recognised standard and security level, such as DIN 66399, and names BSI-approved erasure tools as an option (ASST.7.3.3). Choose techniques that meet those standards.
ASST.7.4 Recovery test to confirm deletion Wiederherstelltest 85%
Rationale
MP-06(01) verifies sanitisation actions, and MP-06(02) tests sanitisation equipment and procedures. Trying to recover the data with recovery tools is one way to run that verification.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ASST.7.5 Destruction equipment for paper documents Vernichtungseinrichtungen
Rationale
MP-06 sanitises non-digital media too, for example by shredding paper. MP-04 keeps media physically protected until they are destroyed or sanitised with approved equipment.
Gaps
GS++ asks for destruction equipment, such as shredders or locked bins, at every site that handles paper documents, protected from unauthorised access. Install and secure that equipment at each of those sites.
ASST.7.6 Authorisation of asset disposals Autorisierung von Veräußerungen
Rationale
MP-06(01) reviews, approves, tracks and documents sanitisation and disposal actions. PE-16 authorises and controls system components that leave the facility. SR-12 disposes of components with defined techniques.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ASST.7.7 Removing labels before disposal Beschriftungen entfernen
Rationale
MP-06 sanitises media, which removes digital identifiers such as hostnames and stored accounts. SR-12 disposes of components with defined techniques, which can include removing identifying labels.
Gaps
GS++ asks the organisation to remove every label that links an asset to it before disposal, such as asset tags and logo stickers. Add that step to your disposal techniques.
PERS.1.1 Personnel: procedures and rules Verfahren und Regelungen
Rationale
PS-01 sets personnel security policy and procedures, documents them, gives them to the roles that need them and names an official to manage them. AT-01 does the same for awareness and training, which covers the training and development of staff.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.1.2 Personnel: regular review Regelmäßige Überprüfung
Rationale
PS-01 reviews and updates the personnel security policy and procedures at a set frequency and after defined events. AT-01 sets the same review cycle for the awareness and training policy and procedures.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.2.1 Tasks with boundaries and interfaces Aufgaben
Rationale
PM-01's information security programme plan assigns roles and responsibilities and sets the coordination between organisational entities. PS-09 writes security roles and responsibilities into position descriptions.
Gaps
GS++ asks the organisation to define tasks for every activity in scope, such as network monitoring or penetration testing. Each task needs clear boundaries and interfaces to the others. Draw them up from GS++'s practices and requirements.
PERS.2.2 Roles with objectives and qualifications Rollen
Rationale
PM-13 sets up a workforce programme that defines the knowledge, skills and abilities security roles need. PS-09 writes security and privacy roles and responsibilities into position descriptions.
Gaps
SP 800-53 covers security and privacy roles. GS++ asks for roles for every activity in scope, each with its objectives, tasks, competences and qualifications. Extend your role descriptions to all those activities.
PERS.2.3 Separation of roles Rollentrennung
Rationale
AC-05 has the organisation identify duties that need separating, such as directory and virtualisation administration, and support the separation with access authorisations (PERS.2.3.1, PERS.2.3.2). CA-02(01) uses independent assessors, which separates implementing security requirements from checking them (PERS.2.3.3).
Gaps
GS++ names the pairs of duties to separate, such as implementation and testing (PERS.2.3.4). AC-05 lets you choose the duties, so include every pair GS++ names.
PERS.2.4 Responsibilities for roles Zuständigkeiten
Rationale
In PL-02, each system's security plan names the people who fill its roles. PM-01's programme plan assigns roles and responsibilities across the security programme.
Gaps
GS++ asks for enough staff in every role, with deputies where the role needs them. Check staffing for each role and name deputies yourself.
PERS.3.1 Confidentiality in the employment or service contract Dienst- oder Arbeitsvertrag 85%
Rationale
PS-06 has staff sign access agreements, such as non-disclosure agreements, before they get access. PS-06(03) covers the duties to protect organisational information that continue after employment ends.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
PERS.3.2 Procedural instructions on joining Verfahrensanweisungen
Rationale
PL-04 gives new users the rules of behaviour and has them acknowledge the rules before they get access. AT-02 includes security literacy training in the initial training for new users.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.3.3 Trade and business secrets Betriebs- und Geschäftsgeheimnisse
Rationale
PL-04 sets rules of behaviour that state each user's responsibilities for handling information. PS-06 has staff sign non-disclosure agreements, and PS-06(03) tells them at the start about duties that continue after they leave.
Gaps
GS++ asks the organisation to define which information counts as a trade or business secret, such as customer data or patents. Write that definition and give it to new staff when they join.
PERS.3.4 Job descriptions Stellenbeschreibungen
Rationale
PS-09 writes security roles and responsibilities into position descriptions. PS-02 assigns each position a risk designation and the screening criteria that go with it.
Gaps
GS++ asks for a full job description before the organisation advertises a post, with its tasks, responsibilities, authority and security criteria. Write it at that point and include the risk designation from PS-02.
PERS.3.5 Checking application documents Prüfung der Bewerbungsunterlagen
Rationale
PM-13 sets standards for measuring the qualifications of applicants for security positions. PS-03 screens people before they get access, and that screening can confirm the qualifications they claim.
Gaps
GS++ asks the organisation to check every applicant's qualifications against their application documents before filling a post. PM-13 sets standards for security positions, so apply the check to all posts.
PERS.3.6 Trustworthiness of applicants Vertrauenswürdigkeit von Bewerbenden
Rationale
PS-03 screens people before they get access, for example with background checks. PS-02 sets screening criteria for each position, with deeper checks for security-relevant posts (PERS.3.6.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.3.7 Onboarding new staff Einarbeitung
Rationale
AT-02 gives new users initial security literacy training. AT-03 gives role-based training before staff take up their assigned duties, so they learn the security side of their role from the start.
Gaps
GS++ asks for structured onboarding that introduces new staff to their tasks and systems as well as to security. Plan that onboarding beyond the training these controls set.
PERS.4.1 Review of qualification needs Qualifikationsbedarf
Rationale
PM-13 sets up a workforce development programme that defines the knowledge and skills security staff need and develops them. AT-03 gives role-based training at a set frequency and updates its content regularly.
Gaps
GS++ asks for a regular review of each staff member's qualification needs against their tasks. An annual training plan for each team is one way to do it. Set up that review for all staff.
PERS.4.2 Role-specific training and awareness Rollenspezifische Schulungen und Sensibilisierungen
Rationale
AT-02 gives all users literacy and awareness training when they join and at a set frequency after that. AT-03 adds role-based training before staff take up their duties, at a set frequency and when systems change. SA-16 has the developer provide training on the product's security functions, which serves as product-specific training for administrators (PERS.4.2.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.5.1 Disciplinary action Maßregelung 90%
Rationale
PS-08 sets up a formal sanctions process for staff who fail to comply with security and privacy policies and procedures. Breaches of security instructions then lead to defined measures.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
PERS.5.2 Insider threats Innentäter
Rationale
PM-12 sets up an insider threat programme with a cross-discipline team to handle cases. AT-02(02) trains staff to recognise and report signs of insider threat. SI-04 monitors systems for unauthorised use, and SI-04(19) adds closer monitoring of people identified as higher risk.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.5.3 Trustworthiness check for security-critical roles Vertrauens-Check sicherheitskritischer Rollen
Rationale
PS-02 assigns risk designations that identify the security-critical positions. PS-03 rescreens the people in them at a set frequency and when defined conditions arise.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
PERS.6.1 Procedure for staff leaving Vorgehensweise für den Weggang
Rationale
PS-04 disables system access when someone leaves, revokes their credentials, holds an exit interview and retrieves organisational property. AC-02 tells account managers about leavers and removes their accounts in step (PERS.6.1.1). PE-02 removes leavers from the facility access list.
Gaps
GS++ asks for each of the leaver's responsibilities to pass to someone else (PERS.6.1.2). Assign each one to a named person or role as part of the leaving process.
BES.1.1 Procurement: procedures and rules Verfahren und Regelungen
Rationale
SA-01 sets acquisition policy and procedures, documents them, gives them to the roles that need them and names an official to manage them. SR-01 does the same for supply chain risk management, which covers the security side of choosing suppliers and contracts.
Gaps
GS++ asks for each procurement task to go to a named person or role. SP 800-53 sets roles and responsibilities at the level of the policy, so assign the tasks yourself.
BES.1.2 Procurement: regular review Regelmäßige Überprüfung
Rationale
SA-01 reviews and updates the acquisition policy and procedures at a set frequency and after events the organisation defines. SR-01 does the same for the supply chain risk management policy and procedures.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.1.3 Register of suppliers and service providers Lieferanten- und Dienstleisterverzeichnis
Rationale
PM-30(01) identifies and prioritises the suppliers of critical products and services. SR-04 records where delivered components come from, and SR-04(01) identifies the elements and people across the whole supply chain (BES.1.3.1).
Gaps
SP 800-53 asks you to identify critical suppliers. GS++ asks for a register of every direct supplier and service provider, with contact details and what each one delivers. Keep that register yourself.
BES.1.4 Outsourcing strategy Outsourcing-Strategie
Rationale
PM-30 sets an organisation-wide strategy for the supply chain risks of acquiring systems and services, which covers the risk side of an outsourcing strategy. SA-09(01) assesses risk before security services are outsourced and has named roles approve the move (BES.1.4.1).
Gaps
GS++ asks for a strategy that also sets out the goals and opportunities of outsourcing, approved by top management. SA-09(01) asks for approval of outsourced security services, so extend that approval to the whole strategy.
BES.1.5 Authorising the cloud deployment model Autorisierung des Bereitstellungsmodells
Rationale
CA-06 has an authorising official approve the cloud service for use and accept the controls it inherits from the provider. That decision covers the chosen deployment model and its shared responsibility. SA-09(01) has named roles approve the outsourcing, and SA-09 sets out oversight roles and responsibilities for the external service.
Gaps
GS++ asks for a decision on the deployment model of each cloud service, such as public, private, community or hybrid cloud. Name the model in each authorisation.
BES.1.6 Documenting the cloud deployment model Dokumentation des Bereitstellungsmodells
Rationale
PL-02 has the security plan describe the operating environment, dependencies on external services and the controls in place, inherited ones included. SA-09 defines and documents the oversight and user roles and responsibilities for each external service, which records the split of shared responsibility.
Gaps
GS++ asks for the chosen deployment model of each cloud service to be on record. Add it to the security plan next to the split of responsibilities.
BES.1.7 Agreeing shared responsibility with the cloud provider Vereinbarung der geteilten Verantwortung
Rationale
SA-04 writes the allocation of security responsibility between the parties into the acquisition contract. SA-09 requires the provider to meet the organisation's security requirements and defines each side's roles and responsibilities.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.2.1 Recording procurement needs Erfassung des Bedarfes
Rationale
SA-02 determines the security requirements of a system or service during business planning. SA-04 puts functional requirements and the intended operating environment into the acquisition, which covers system prerequisites (BES.2.1.3). PM-11 defines business processes and their protection needs, the core of a business process profile (BES.2.1.2). CM-10 keeps software use within licence terms and tracks licences (BES.2.1.5). MA-06 obtains maintenance support and spare parts within set times (BES.2.1.6).
Gaps
GS++ names the purpose of use and compatibility with your interfaces, network connection, administration model and data management model. Its business process profile also shows interfaces and dependencies between processes. Record each of these by name.
BES.2.2 Documenting jurisdiction and data location for cloud services Dokumentation des Rechtsraums und der Datenlokation
Rationale
CM-12 identifies and documents where information is processed and stored. SA-09(05) sets the locations where the provider may process and store data and run its services.
Gaps
GS++ asks you to record the provider's legal jurisdiction as well as the data location. The two can differ, as with a provider headquartered outside Europe that stores data at European sites.
BES.2.3 Agreeing jurisdiction and data location with the cloud provider Vereinbarung des Rechtsraums und der Datenlokation
Rationale
SA-04 writes the location requirements into the contract with the provider as security requirements. SA-09(05) restricts processing, storage and services to the locations the organisation permits.
Gaps
GS++ asks you to agree the legal jurisdiction with the provider as well as the data location. SA-09(08) covers US jurisdiction, so write the jurisdiction you need into the contract.
BES.2.4 Consulting users on procurement needs Anhörung Nutzender 20%
Rationale
SA-02 determines the security requirements for a system or service during mission and business planning. That is the step where the needs of users feed into a procurement.
Gaps
GS++ asks you to consult users when you capture a procurement need, for example through a survey or a test group. Build that step into your procurement process.
Mapped Controls
BES.2.5 Consulting administrators on procurement needs Anhörung Administrierender 25%
Rationale
SA-02 determines the security requirements for a system or service during mission and business planning. That is the step where administrators can raise maintainability and compatibility before a purchase.
Gaps
GS++ asks you to consult administrators when you capture a procurement need, so they can check how the product will be run and updated. Add them to your needs assessment.
Mapped Controls
BES.2.6 Outsourcing based on business process profiles Outsourcing auf Grundlage der Geschäftsprozessprofile
Rationale
PM-11 defines business processes and their protection needs, which gives the profiles an outsourcing decision rests on. SA-09(01) assesses risk before outsourcing and has named roles approve it.
Gaps
GS++ asks management to approve each outsourcing contract on the basis of the process profiles. SA-09(01) asks for this approval for security services, so extend it to every outsourced process.
BES.3.1 Classifying supplier relationships Klassifizierung von Lieferantenbeziehungen
Rationale
AC-21 helps staff decide whether a partner may receive given information, which is what a supplier class is for. PM-30(01) identifies and prioritises suppliers of critical items. SR-06 assesses each supplier's supply chain risks, such as foreign ownership or influence, which gives the inputs for a class.
Gaps
GS++ asks you to place every supplier relationship in a security class, for example by the data shared or the supplier's function. Set up that classification scheme yourself.
BES.3.2 Supplier selection criteria Auswahlkriterien
Rationale
SR-05 sets acquisition strategies and methods for choosing trustworthy suppliers, and SR-05(02) assesses candidates before selection. SR-06 assesses each supplier's supply chain risks, including its processes and controls, by the organisation itself or a third party. SR-03(01) uses a diverse set of sources, which limits dependence on single suppliers (BES.3.2.2).
Gaps
GS++ asks you to weigh a supplier's financial stability and its certificates or attestations when you choose it (BES.3.2.1). Add both to your selection criteria.
BES.3.3 Excluding unreliable suppliers Unzuverlässige Lieferanten
Rationale
SR-05 sets acquisition strategies and methods that guard against untrusted sources, for example trusted or controlled distribution. SR-11 sets anti-counterfeit procedures that keep components from unknown sources out of the system.
Gaps
GS++ asks you to ban purchases from unknown or unreliable sources. Write that ban into your procurement rules.
BES.4.1 Classifying procurement projects Klassifizierung von Beschaffungsvorhaben
Rationale
RA-02 categorises the system and the information a procurement affects, which gives the basis BSI suggests for the class. RA-03(01) assesses supply chain risk for the system, component or service being bought.
Gaps
GS++ asks you to give each procurement project a class. Where a supplier has its own classification scheme, map your classes to the supplier's.
BES.4.2 Documenting procurement criteria Dokumentation der Beschaffungskriterien
Rationale
SA-04 records the criteria for each acquisition, such as security requirements, strength of mechanism, assurance and documentation requirements and acceptance criteria. SR-05 sets acquisition strategies and procurement methods that address supply chain risk.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.4.3 Procurement based on the defined criteria Beschaffung anhand der Kriterien
Rationale
SA-04 puts the defined requirements and criteria into each acquisition contract, so each purchase follows them. SR-05(02) assesses the system, component or service against them before selection and acceptance.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.4.4 Contract template for outsourcing Vertragsvorlage für Outsourcing
Rationale
SA-04 has the organisation state its security requirements in standardised contract language. SA-09 sets the requirements and controls that providers of external services must meet.
Gaps
GS++ asks for a standard policy for outsourcing contracts. It sets basic criteria, such as data locations, test and approval procedures and compliance risks at subcontractors. Use it for every outsourcing contract.
BES.4.5 Security by design Security by Design
Rationale
SA-08 applies security engineering principles in specification, design and development. SA-04 carries the security requirements into the contract, and SA-04(03) asks the developer to show a secure development life cycle (BES.4.5.1). SA-15 asks for a documented development process that addresses security. SA-17 asks the developer for a security architecture and design, which counts as agreed security by design once it is part of the contract. SC-04 prevents information transfer through shared resources, the basis of tenant separation (BES.4.5.2).
Gaps
GS++ asks for a defined tenant separation agreed with the outsourcing provider. SC-04 covers shared resources, which is part of that, so set out the full separation in the contract.
BES.4.6 Security by default Security by Default
Rationale
SA-04(05) asks for delivery with defined security configurations in place as the default, and SA-08(23) applies the principle of secure defaults. SC-08 and SC-28 protect information in transit and at rest, here encryption by the provider (BES.4.6.2). SR-09 sets a tamper protection programme that covers the delivery route (BES.4.6.3).
Gaps
GS++ also asks the organisation to agree how a service provider authenticates anyone acting for it before giving access to its information or services (BES.4.6.1). Agree concrete methods with each provider, such as a customer password, one-time codes or passkeys.
BES.4.7 ISMS at the service provider ISMS beim Dienstleister
Rationale
SA-04 writes the organisation's security and assurance requirements into the contract. SA-09 requires the provider to meet those requirements and to employ the controls the organisation defines.
Gaps
GS++ asks the outsourcing provider to run an information security management system (ISMS), which a certificate can show. Name the ISMS and the certificate you accept in the contract.
BES.4.8 Evidence of conformity from the supplier Konformitätsnachweise
Rationale
SA-04 puts assurance and documentation requirements into the contract, which set the evidence the supplier must provide. CA-02(03) uses assessments by external organisations, such as certificates and attestations (BES.4.8.1, BES.4.8.2). SR-06(01) has third parties test and analyse the supplier. SR-08 sets agreements with suppliers to share the results of assessments or audits.
Gaps
GS++ also asks for an analysis of the provider's infrastructure by BSI's IT-Grundschutz method (BES.4.8.3). It asks the provider to disclose the risk analysis from its ISMS (BES.4.8.4). Write both into the contract.
BES.4.9 Security screening of supplier staff Sicherheitsüberprüfung (extern)
Rationale
PS-03 screens individuals before they get access. PS-07 sets personnel security requirements for external providers, screening included, and requires them to comply. SA-21 sets screening criteria for the developer's staff where the supplier develops the system.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.5.1 Security competences of supplier staff Kompetenzen
Rationale
PS-07 sets personnel security requirements for external providers, including the security roles and responsibilities their staff must meet. AT-03 gives role-based security training to people in security roles, which defines the knowledge each role needs.
Gaps
GS++ asks you to agree the information security competences that supplier staff must have, such as minimum skills or certificates. Write those competences into the contract.
BES.5.2 Service level agreement Service Level Agreement
Rationale
SA-04 writes availability and other security requirements into the contract. SA-09 sets the requirements and controls providers must meet and monitors their compliance, which is the basis for agreed service levels.
Gaps
GS++ asks for measurable service levels, such as availability as a percentage, recovery time objectives and support hours. Set those figures in the agreement with the provider.
BES.5.3 Compliance obligations in supplier contracts Compliance-Verpflichtungen
Rationale
SA-04 writes security and privacy requirements drawn from laws, regulations and contracts into the acquisition contract. SA-09 requires providers to comply with the organisation's security and privacy requirements, legal ones included.
Gaps
GS++ asks suppliers to meet all your compliance obligations, such as the intellectual property rights of third parties. Add obligations outside security and privacy to the contract yourself.
BES.5.4 Information security controls in supplier contracts Informationssicherheitskontrollmechanismen
Rationale
SA-04 puts the controls needed to meet the security requirements into the contract. SA-09 requires providers of external services to employ the controls the organisation defines.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.5.5 Rules on the use of data and assets Nutzungsregelungen
Rationale
SA-04(12) writes the organisation's ownership of its data into the contract. SA-09(05) restricts processing and storage to the locations the organisation permits (BES.5.5.1). AC-02 approves and manages accounts for supplier staff against defined criteria (BES.5.5.2).
Gaps
GS++ asks for rules on when and where the provider may use your data and related assets. It also asks you to name the uses you forbid. Write those rules into the contract.
BES.5.6 Rules for subcontracting Vergabe von Unteraufträgen
Rationale
SA-09 holds external providers to the organisation's requirements for the services they pass on to others. SR-03(03) flows the contract's controls down to subcontractors (BES.5.6.1). SR-04(02) tracks critical components through the supply chain (BES.5.6.3).
Gaps
GS++ asks you to approve each subcontractor your supplier uses (BES.5.6.2). Write that approval step into the contract with the supplier.
BES.5.7 Training on delivered security mechanisms Schulung 95%
Rationale
SA-16 requires the developer to train the organisation's staff in the correct use of the security functions it delivers, such as encryption or access controls.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BES.5.8 Rights to intellectual property created under the contract Rechte für geistges Eigentum 25%
Rationale
SA-04(12) writes the organisation's ownership of its data into the contract. That is the nearest SP 800-53 provision to ownership of work created under a contract.
Gaps
GS++ asks you to agree who owns the intellectual property developed during the contract, such as code, data models, concepts and documentation. Write those ownership rights into the contract.
Mapped Controls
BES.5.9 Handling changes to the service Umgang mit Änderungen
Rationale
SA-09 requires the provider to follow the organisation's requirements and agreed controls for the service. SA-10 has the developer control changes, implement only the changes the organisation approves and document their security impact (BES.5.9.1).
Gaps
GS++ asks for agreed rules on changes, such as how much notice the provider gives before it changes the service. Set those notice periods in the contract.
BES.5.10 Handling incidents with suppliers Behandlung von Vorfällen
Rationale
SR-08 sets agreements with suppliers to notify the organisation of compromises (BES.5.10.2). IR-04(10) coordinates incident handling with the organisations in the supply chain. IR-06(03) sends incident information to the provider of the affected product or service. SA-10 has the developer track security flaws and their resolution and report them (BES.5.10.3).
Gaps
GS++ also asks the supplier for a vulnerability disclosure process that follows a recognised standard (BES.5.10.3.1). It asks for a way to settle disputes and for remedies when the supplier breaches the contract. Write these into the contract.
BES.5.11 Right to audit Recht auf Audit
Rationale
SA-09 sets methods to monitor the provider's compliance with its controls on an ongoing basis. SR-06 assesses and reviews suppliers, either by the organisation itself or by an independent third party.
Gaps
GS++ asks for your right to audit the provider's security processes and measures. Write that right into the outsourcing contract.
BES.5.12 Duty to report on the effectiveness of security measures Informationspflichten
Rationale
SA-04(08) asks the developer for a plan to monitor control effectiveness continuously. SA-09 monitors the provider's compliance with its controls on an ongoing basis. SR-08 sets agreements for suppliers to report the results of assessments or audits.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.5.13 Provision of backups by the provider Bereitstellung von Datensicherungen
Rationale
CP-09 backs up user and system information at set frequencies and protects the backups. SA-09 requires the provider to employ the controls the organisation sets, which can include regular delivery of backups.
Gaps
GS++ asks the provider to hand backup copies to you regularly. It also asks for your data in a standard format (BES.5.13.1). Name both in the contract.
BES.5.14 Deletion rules for data held by the provider Löschregeln
Rationale
SI-12 manages and retains information in line with laws and other requirements, and SI-12(03) disposes of it at the end of the retention period. SA-09 requires the provider to apply the organisation's retention and deletion rules.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.6.1 Revoking access rights on termination Entziehung der Zugangsberechtigungen
Rationale
AC-02 disables and removes accounts when they are no longer needed. PS-07 requires external providers to report the transfer or termination of their staff who hold credentials or badges.
Gaps
GS++ asks you to agree that all access tied to the contract ends when the contract does. That covers accounts, technical interfaces, access cards and VPN access. Make contract end a trigger for revoking them.
BES.6.2 Deleting data on termination Löschung von Daten
Rationale
SA-04(12) requires the contractor to remove all organisational data from its systems and return it. MP-06 sanitises media with techniques that leave the data unrecoverable (BES.6.2.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.6.3 Data portability on termination Übertragbarkeit von Daten 35%
Rationale
SA-04(12) puts data ownership into the acquisition contract. It requires the contractor to remove the organisation's data from its systems and return it, here when the contract ends.
Gaps
GS++ asks for portability of configurations and functionality as well as data, in a complete, machine-readable format. Agree that format in the contract so you can move to a new provider.
Mapped Controls
BES.6.4 Handover of support services on termination Übertragung von Supportdienstleistungen 35%
Rationale
SA-22 provides alternative sources of support for system components, in house or from another provider. It applies when the original support ends, as it does when a contract ends.
Gaps
GS++ asks the outgoing provider to hand over support in an orderly way, with documentation, maintenance logs, access details and contacts. Agree that handover in the contract.
Mapped Controls
BES.6.5 Handling retained records on termination Behandlung aufzubewahrender Aufzeichnungen
Rationale
AU-11 keeps audit records for the retention period the organisation sets. SI-12 manages and retains information as laws, regulations and other requirements demand. Together they set which records to retain and for how long.
Gaps
GS++ asks you to agree controls with the provider over records it keeps after the contract ends. Those controls keep the records complete and protected. Write them into the contract.
BES.6.6 Return of assets on termination Rückgewähr von Assets 40%
Rationale
SA-04(12) puts data ownership into the acquisition contract. It requires the contractor to remove the organisation's data from its systems and hand it back, which covers data as one kind of asset.
Gaps
GS++ asks for the return of every asset the organisation provided, such as IT systems, storage media and paper copies, when the contract ends. Agree their return in the contract.
Mapped Controls
BES.7.1 Incoming inspection against acceptance criteria Eingangskontrolle
Rationale
SA-04 sets acceptance criteria in the contract, and SR-05(02) assesses the product or service against them before acceptance. CM-04(01) tests changes in a separate environment for flaws and incompatibility (BES.7.1.1). CA-02 assesses controls before use, including the criteria for the network connection (BES.7.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.7.2 Processes before connecting to the provider's network Prozesse vor Netzanbindung
Rationale
CA-03 approves the connection to the provider's network under an agreement that documents interfaces, security requirements and responsibilities. SC-07 connects to external networks only through managed interfaces with boundary protection.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.7.3 Consulting those involved in the outsourced process Anhörung Prozessbeteiligter 0%
Rationale
SP 800-53 leaves consulting the people involved in an outsourced process to the organisation.
Gaps
No SP 800-53 control is mapped to this requirement. GS++ asks the organisation to consult every person or role involved in an outsourced process, such as IT operations staff, security experts or the legal department.
BES.7.4 Completeness of delivered documentation Vollständigkeit der Unterlagen
Rationale
SA-17 asks for the developer's security architecture (BES.7.4.1). SA-05 obtains documentation on secure configuration and security functions (BES.7.4.2, BES.7.4.3). SA-04(01), (02) and (09) ask for descriptions of controls and design and the ports, protocols and services in use (BES.7.4.5). CM-08 inventories the delivered hardware and software (BES.7.4.4). SR-04(04) validates the composition and provenance of components, which a software bill of materials records. SA-09 documents the split of responsibilities, and SA-09(02) identifies the ports, protocols and services each external service needs (BES.7.4.6, BES.7.4.8).
Gaps
GS++ also asks for an outsourcing register and a service profile for each cloud service (BES.7.4.9, BES.7.4.10). It asks you to keep a software bill of materials (SBOM) to a recognised standard for delivered software. Add these to your records.
BES.8.1 Keeping alternative suppliers available Bereithaltung alternativer Lieferanten
Rationale
SR-03(01) uses a diverse set of sources for defined components and services. SR-05(01) ensures an adequate supply of critical components, which reduces dependence on a single supplier.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BES.8.2 Procedures for transferring outsourced business processes Verfahren zur Übertragung von Geschäftsprozessen
Rationale
CP-02 plans how essential functions keep running through a disruption, such as the loss of a provider. CP-02(07) coordinates the plan with the providers' own plans. CP-07 sets up an alternate processing site with agreements to transfer and resume operations.
Gaps
GS++ asks for procedures to transfer outsourced business processes when the contract ends, planned or unplanned. List alternative providers that offer the security level you need.
BES.8.3 Internal resources for the end of an outsourcing contract Ressourcensouveränität
Rationale
CP-02 assigns contingency roles to named people, and CP-02(02) plans the capacity needed for processing and support during contingency operations. SA-02 determines and allocates the resources needed to protect the system or service.
Gaps
GS++ asks you to keep enough qualified staff and infrastructure in house to take over if the outsourcing contract ends, planned or unplanned. Plan that capacity and budget for it.
BES.8.4 Custom implementation of critical components Individuelle Implementierung kritischer Komponenten 90%
Rationale
SA-20 has critical components re-implemented or custom developed for the organisation. The organisation chooses which components count as critical, such as cryptographic modules or authentication mechanisms.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BES.8.5 Escrow agreements Treuhand
Rationale
SA-15(11) has the developer archive the released system with its source code and supporting evidence. SA-22 provides alternative support when the vendor's support ends, which an escrow agreement makes possible.
Gaps
GS++ asks for escrow agreements with a trusted third party. Set release conditions in them for the source code and for the keys or passwords needed to use it.
DLS.1.1 Service providers: procedures and rules Verfahren und Regelungen
Rationale
SA-01 sets acquisition policy and procedures, external services included, and names an official to manage them. It documents them and gives them to the roles that need them. SR-01 does the same for supply chain risk management, which covers ongoing oversight of providers. SA-09 defines oversight roles for external service providers and monitors their compliance, which is how the organisation controls its service contracts.
Gaps
SA-09 covers oversight while a contract runs. GS++ also asks for a procedure to end service contracts in an orderly way, so add the exit steps to your procedures.
DLS.1.2 Service providers: regular review Regelmäßige Überprüfung
Rationale
SA-01 c reviews and updates the acquisition policy and procedures at a set frequency. It also reviews them after defined events, such as a serious security incident or new legal requirements. SR-01 c does the same for the supply chain risk management policy and procedures.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DLS.2.1 Multi-factor authentication for online services Mehr-Faktor-Authentifizierung 90%
Rationale
IA-02(01) and (02) ask for multi-factor authentication on privileged and non-privileged accounts. For online services, such as cloud office applications, that means a second factor like a one-time password.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
DLS.2.2 Transport encryption to the service provider Transportverschlüsselung
Rationale
SC-08(01) uses cryptography to protect the confidentiality and integrity of data on its way to the provider. SC-13 sets the type of cryptography for each use, for example to a recognised standard.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DLS.2.3 Full encryption before transfer to the service provider Vollverschlüsselung
Rationale
SA-09(06) has the organisation keep exclusive control of the keys for data stored at or sent through an external provider. SC-12 manages those keys so they stay with the organisation. SC-28(01) encrypts the data at rest, for example per file or in an encrypted container.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DLS.3.1 Service provider compliance with security requirements Einhaltung der Sicherheitsvorgaben
Rationale
SA-09 c monitors the provider's compliance with security requirements on an ongoing basis. SR-06 assesses and reviews suppliers at a set frequency. CA-02(03) uses the results of assessments by external organisations, such as audits or certificates (DLS.3.1.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DLS.3.2 Checkup of the outsourcing decision Checkup
Rationale
RA-03 updates the risk assessment at a set frequency and when threats or conditions change. RA-03(01) does the same for supply chain risk. SR-06 reviews suppliers and the services they provide at a set frequency.
Gaps
GS++ asks you to review the outsourcing decision itself against your business process profiles. Use those profiles as input each time you update the supply chain risk assessment.
DLS.3.3 Outsourcing strategy check Strategie-Check
Rationale
PM-30 reviews and updates the supply chain risk management strategy when the organisation changes. PM-11 reviews and revises the business process definitions and their protection needs, which the strategy depends on.
Gaps
GS++ asks you to check the outsourcing strategy for completeness and correctness whenever a business process profile changes. Make each change to a profile a trigger for that check.
DLS.3.4 Consulting the service provider on security measures Anhörung 20%
Rationale
SA-09 b defines the oversight roles and responsibilities for an external service. That oversight gives the organisation a channel to hear the provider on planned security measures.
Gaps
GS++ asks you to consult the provider on security measures for the target objects it serves. Tell the provider what you plan and give it time to comment.
Mapped Controls
DLS.3.5 Blocking unreliable service providers Blockierung unzuverlässiger Dienstleister
Rationale
SR-06 assesses suppliers and identifies the unreliable ones. SR-05 shapes acquisition strategies and methods to exclude untrusted suppliers. AC-20 b prohibits the use of named external systems, such as a service run by an unreliable provider. SR-03(03) carries the contract controls down into the contracts of sub-providers.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DLS.3.6 Portability of the outsourced process Portabilität
Rationale
CP-07 sets up an alternate processing site where operations can resume, which here means a site away from the provider. CP-04(02) tests the contingency plan at that alternate site.
Gaps
GS++ asks for regular tests that the outsourced process works in an environment away from the provider. Add the outsourced process to your contingency plan tests at the alternate site.
DLS.4.1 Decommissioning a service before the contract ends Dekomissionierung
Rationale
SA-04(12) has the contract require the provider to return the organisation's data and remove it from its systems at the end. AC-02 disables the accounts used for the contract when the need for them ends (DLS.4.1.2). PE-02 removes the provider's staff from the facility access list (DLS.4.1.2). CP-04 tests can show that processing runs independently of the provider (DLS.4.1.1).
Gaps
GS++ asks for a planned procedure to decommission the whole service relationship before the contract ends. Write that procedure yourself, with the data return and the removal of access rights as steps in it.
TEST.1.1 Changes and tests: procedures and rules Verfahren und Regelungen
Rationale
CM-01 sets configuration management policy and procedures, documents them, gives them to the roles that need them and names an official to manage them. CM-03 brings changes under change control, including adding and removing components. CM-09 sets out roles and responsibilities for configuration management in a plan, which assigns the tasks (TEST.1.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
TEST.1.2 Changes and tests: regular review Regelmäßige Überprüfung 95%
Rationale
CM-01 has the organisation review and update its configuration management policy and procedures at a set frequency and after defined events. That covers both the regular review and the review after an event, such as a serious security incident.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
TEST.1.3 Restricting changes to administrators Einschränkung von Änderungen
Rationale
CM-05 defines and enforces access restrictions for changes, and CM-05(05) limits who holds change privileges in production. AC-06 applies least privilege, so only the administrators who need change rights get them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
TEST.2.1 Version history of changes Versionshistorie
Rationale
CM-03 documents decisions on changes and keeps records of the changes made. CM-02(03) keeps previous versions of the baseline configuration, which gives a history of how the system has changed.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
TEST.2.2 Impact assessment before changes Folgenabschätzung
Rationale
CM-03 sets the types of change that go through change control, which sorts changes into categories (TEST.2.2.1). CM-03(01) documents each proposed change (TEST.2.2.2). CM-04 analyses the security and privacy impact of a change before it goes ahead, including the effect on dependent systems (TEST.2.2.3).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
TEST.3.1 Security testing of changes Sicherheitstest
Rationale
CM-03(02) tests each change and documents the results before it goes live (TEST.3.1.1). CM-04(01) tests in a separate environment (TEST.3.1.5), and CM-04(02) checks the controls after the change. SA-03(02) controls the use of live data in test environments (TEST.3.1.4). SA-11 has developers test their work, with penetration testing in SA-11(05) and fuzzing as part of dynamic analysis in SA-11(08). SI-07 checks the integrity of software (TEST.3.1.3). SR-05 keeps out components from untrustworthy sources (TEST.3.1.2).
Gaps
For a higher security level, GS++ suggests load tests and chaos engineering, which simulates disruptions to test resilience. It also suggests composition analysis, which tests what each change is made of. Add the tests you choose to your test plan.
TEST.3.2 Test coverage Testabdeckung
Rationale
SA-11 has developers test their work, and SA-11(07) checks that testing covers the required controls at a set breadth and depth. PM-14 reviews testing plans against the organisation's risk priorities.
Gaps
GS++ asks for a regular review of test coverage, which includes code coverage. Measure how much of the code your tests run, as well as which controls they check.
TEST.4.1 Authorisation of changes Autorisierung von Änderungen
Rationale
CM-03 approves or rejects each change after weighing its security impact, and records the decision (TEST.4.1.3). AC-05 separates the people who approve a change from those who carry it out (TEST.4.1.1). CM-04(01) tests changes in a separate environment before they reach production (TEST.4.1.2).
Gaps
GS++ asks for a staging environment that matches production as closely as possible (TEST.4.1.2). Build the separate test environment of CM-04(01) to mirror production.
TEST.4.2 Signature on the approval statement Signatur
Rationale
AU-10 gives irrefutable evidence that a named person approved the change, for example through a digital signature. CM-03 documents each decision to approve a change.
Gaps
GS++ accepts a handwritten signature on the approval statement as well as a digital one. AU-10 covers the digital kind, so file signed paper approvals with the change records.
TEST.4.3 Fallback solution for changes Rückfallösung
Rationale
CM-02(03) keeps previous configurations, so a change can be rolled back. CP-09 backs up the system, which lets you restore the state from before a failed change. CP-10 recovers the system to a known state after a failure.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
TEST.4.4 Rules for emergency changes Geregelte Notfalländerungen
Rationale
CM-03 brings unscheduled changes under change control, with defined review and approval. CM-09 sets the roles and responsibilities for configuration management in a plan. SI-02 installs security fixes within set times, and a critical fix is a typical emergency change.
Gaps
GS++ asks for a separate procedure for emergency changes, with the resources it needs and the minimum test steps each change must pass. Add that procedure to your change rules.
TEST.5.1 Informing groups affected by a change Information betroffener Kreise 45%
Rationale
CM-03(01) notifies the personnel the organisation chooses about each proposed change, and again once the approved change is complete. This keeps the people in the change process informed.
Gaps
GS++ asks you to inform everyone a change affects, such as users and the monitoring team. Tell them about expected downtime and any settings they need to change themselves.
Mapped Controls
TEST.5.2 Encrypted deployment Verschlüsselte Bereitstellung
Rationale
SC-08 protects the confidentiality and integrity of deployment artefacts in transit to the target environment. SC-13 sets the type of cryptography for each use, including the deployment channel.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
TEST.5.3 Gradual rollout of changes Schrittweiser Rollout 25%
Rationale
CM-03 puts approved changes into effect in a controlled way. A gradual rollout, one group at a time, is one way to do that.
Gaps
GS++ suggests rolling out a change in stages, for example one site or one group of users at a time. Plan the stages as part of each change.
Mapped Controls
TEST.5.4 Persistence of changes Persistenz
Rationale
CM-02 writes each change into the baseline configuration, so it survives a rebuild or a restore. CM-04(02) checks after a change that the affected controls work as intended. SI-06 verifies security functions at transitional states, such as startup and restart.
Gaps
GS++ asks you to test that a change stays in place after a system update or a restore from a configuration backup. Add those cases to the tests after each significant change.
TEST.5.5 Deployment retrospective Rückblick
Rationale
CM-03 monitors and reviews the activities linked to each change. CM-04(02) checks after a change that the controls work as intended and meet the security requirements.
Gaps
GS++ asks for a regular review of whether deployments reached their goals. Use the findings to plan later changes and reduce their risks.
GEB.1.1 Buildings: procedures and rules Verfahren und Regelungen 95%
Rationale
PE-01 sets the physical and environmental protection policy and procedures and names an official to manage them. It documents them and gives them to the roles that need them. The policy covers the physical protection of sites that process or store sensitive information.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.1.2 Buildings: regular review Regelmäßige Überprüfung 95%
Rationale
PE-01 c reviews and updates the physical and environmental protection policy and procedures at a set frequency. It also reviews them after defined events, such as a serious security incident or new legal requirements.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.1.3 Authorisation of sites for assets Autorisierung von Standorten
Rationale
PE-23 plans the location of a facility with physical and environmental hazards in mind. CA-02 assesses the controls at a site against set criteria before it goes into use (GEB.1.3.1). PE-17 documents the alternate work sites the organisation allows and assesses their controls.
Gaps
GS++ asks you to authorise each site formally before you place assets there. Base each authorisation on the assessment results and record it.
GEB.1.4 Placing assets outside exposed areas Exponierte Bereiche
Rationale
PE-18 positions system components to minimise damage from hazards and the chance of unauthorised access. That keeps them out of places such as a basement at risk of flooding. PE-23 plans the facility's location with physical and environmental hazards in mind.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.1.5 Structural plans of buildings and utilities Strukturpläne 0%
Rationale
SP 800-53 leaves plans of buildings and sites to the organisation.
Gaps
No SP 800-53 control is mapped to this requirement. GS++ asks for plans of each site: floor plans and the routes of physical perimeters, utility lines, network connections and exits, emergency exits included.
GEB.2.1 Installing security perimeters Installation von Perimetern 85%
Rationale
PE-03 enforces physical access authorisations at the facility's entry and exit points. PE-03(07) adds physical barriers that limit access to the facility.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.2.2 Documentation of public areas Dokumentation öffentlicher Bereiche 55%
Rationale
PE-03 c controls access to the areas the organisation designates as publicly accessible, such as reception or delivery zones.
Gaps
GS++ asks you to document each area open without authentication, with the reason it's open. Record that reason when you designate the area as publicly accessible.
Mapped Controls
GEB.2.3 Reconnaissance from public space Erkundung aus dem öffentlichen Raum
Rationale
PE-18 positions system components to keep their information out of sight and earshot of people near entry points. RA-06 uses technical surveillance countermeasures surveys, which examine the facility inside and out for weaknesses an attacker could exploit.
Gaps
GS++ asks you to test the site's protection against being seen or heard from public space. Run those checks from the public side, as an outsider would.
GEB.2.4 Electromagnetic shielding Elektromagnetische Abschirmung
Rationale
PE-19 protects against information leakage through electromagnetic emanations, such as screen content picked up from outside the building. CA-02 assesses whether controls such as the shielding work as intended.
Gaps
GS++ asks for a specific test of the electromagnetic shielding. CA-02 assesses controls in general, so add the shielding to your assessment plan as a test of its own.
GEB.3.1 Monitoring of entry points Überwachung von Zutrittspunkten
Rationale
PE-06 monitors physical access to the facility. PE-06(01) adds intrusion alarms and surveillance equipment, and PE-06(03) adds video surveillance (GEB.3.1.1). PE-03 has guards or access devices control the entry points. PE-03(02) checks at the perimeter for components or information being taken out (GEB.3.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.3.2 Registration and reception areas Anmelde- und Empfangsbereiche
Rationale
PE-03 controls entry to the facility and access to its publicly accessible areas. It also escorts and controls visitors. PE-08 keeps records of visitor access.
Gaps
GS++ asks you to set up registration and reception areas at each site. Place them where visitors arrive, as the dividing point between public and protected zones.
GEB.3.3 Authentication before entry Authentifizierung vor Zutritt
Rationale
PE-02 keeps the list of people allowed into the facility and issues their credentials. PE-03 checks each person's authorisation before entry, with guards or an access control system (GEB.3.3.1), and keeps access logs (GEB.3.3.2). PE-08 records visitor access, which supports the authorisation of visits (GEB.3.3.3).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.3.4 Visible authorisation badges Berechtigungsmarkierung
Rationale
PE-02 issues authorisation credentials, such as badges, to the people allowed into the facility. PL-04 sets rules of behaviour for users, which can tell them to wear their badges.
Gaps
GS++ asks you to tell users to wear their badges where others can see them, everywhere inside the security perimeter. Put that duty in your rules of behaviour.
GEB.3.5 Burglary resistance Einbruchhemmung 60%
Rationale
PE-03(07) limits access to the facility with physical barriers, such as the walls and doors around server rooms or media archives.
Gaps
GS++ asks for burglary-resistant components built to a recognised standard, such as EN 1627. Choose the resistance class from the risk to the assets and the likely attackers.
Mapped Controls
GEB.3.6 Intrusion alarm systems Einbruchmeldeanlagen 85%
Rationale
PE-06(01) monitors physical access with intrusion alarms and surveillance equipment. PE-06(02) recognises intrusions automatically and starts a response.
Gaps
GS++ asks for intrusion alarm systems built to a recognised standard. Name that standard in your requirements and choose a system that meets it.
Mapped Controls
GEB.3.7 Review of physical access controls Kontrolle der Zutrittskontrolle
Rationale
CA-02 assesses at a set frequency whether physical access controls work as intended. CA-08(03) tests physical access points with announced or unannounced attempts to get past them. PE-06 reviews physical access logs at a set frequency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.4.1 Setting up secure areas Einrichtung 75%
Rationale
PE-03(01) enforces separate physical access authorisations for spaces inside the facility that hold system components, such as server rooms. Each such space then works as a secure area with its own perimeter.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.4.2 Separate authorisation for secure areas Gesonderte Autorisierung
Rationale
PE-02 approves the list of people allowed into the secure area. PE-02(01) grants that access by position or role, and PE-02(03) restricts unescorted access. PE-03(01) enforces those authorisations at the entrance to the secure area.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.4.3 Security airlocks at access points Schleusen 90%
Rationale
PE-03(08) uses access control vestibules at defined entry points. Like an airlock, a vestibule has two doors that open one after the other, so one person or item passes at a time.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.4.4 Single-person entry systems at access points Vereinzelungsanlage 80%
Rationale
PE-03 controls each entry point with physical access devices. PE-03(08) adds access control vestibules, which let one person through at a time and stop tailgating.
Gaps
PE-03(08) names vestibules. GS++ also names turnstiles and similar single-person entry systems, so choose the type that suits each access point.
Mapped Controls
GEB.5.1 Delivery access point Lieferzugang
Rationale
PE-16 authorises and controls the components that enter and leave the facility. Its discussion points to isolating delivery areas from the rest of the facility. PE-03 controls access between the delivery area and the rest of the site.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.5.2 Protection against tampering Schutz gegen Manipulation
Rationale
PE-03(04) keeps system components in lockable casings, and PE-03(05) uses anti-tamper technologies to prevent or detect tampering. SR-09 runs a tamper protection programme for the system and its components.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.5.3 Physical microsegmentation Physische Mikrosegmentierung
Rationale
SC-32 partitions system components into separate physical domains, such as separate racks or rooms. PE-03(01) enforces access authorisations at each of those spaces, which turns them into access-controlled zones inside a shared facility.
Gaps
GS++ asks for building measures that keep the zones apart, such as separate entrances, utilities and ventilation for each zone. Build them into the design of the shared facility.
GEB.6.1 Access to output devices Zugang zu Ausgabesystemen 90%
Rationale
PE-05 controls physical access to output devices, such as printers and monitors. That covers devices that show or print sensitive content, such as the HR department's network printer.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.6.2 Protected placement of IT systems Geschützte Aufstellung
Rationale
PE-18 positions system components to minimise the chance of unauthorised access. PE-03(01) enforces access authorisations to the rooms that hold system components, such as the server rooms for host systems (GEB.6.2.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.6.3 Network components in technical infrastructure rooms Netzkomponenten
Rationale
PE-18 positions network components to minimise damage from hazards and the chance of unauthorised access. PE-03(01) restricts access to the rooms that hold them. PE-04 controls physical access to distribution and transmission lines, for example with locked wiring closets.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.6.4 Standard-compliant data centres Normgerechte Rechenzentren
Rationale
PE-23 plans the location of the facility with physical and environmental hazards in mind. PE-18 positions system components within the facility to minimise damage from those hazards.
Gaps
GS++ asks you to place server rooms only in data centres built and maintained to a recognised standard, such as EN 50600 or ISO/IEC 22237. Make that standard a condition when you choose a data centre.
GEB.7.1 Key custodians for buildings and rooms Schlüsselbeauftragte 60%
Rationale
PE-03 e secures keys, combinations and other physical access devices. PE-03 f keeps an inventory of them, and PE-03 g changes keys and combinations, for example when a key is lost.
Gaps
GS++ asks you to give the management of keys to named people or roles, such as facility management or the reception desk. Name them in your site procedures.
Mapped Controls
GEB.7.2 Safekeeping of keys Verwahrung von Schlüsseln
Rationale
PE-03 e secures keys and other physical access devices. PL-04 sets rules of behaviour that tell users their responsibilities, which can include keeping keys safe.
Gaps
GS++ asks you to tell users how to keep their keys safe, for example by carrying them or locking them in a key cabinet. Add that instruction to your rules of behaviour.
GEB.7.3 Key audit for buildings and rooms Schlüsselaudit 90%
Rationale
PE-03 f inventories keys and other physical access devices at a set frequency. PE-03 g changes keys when one is lost or compromised.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.8.1 Separate storage of business-critical media Gesonderte Aufbewahrung 90%
Rationale
MP-04 physically controls media and stores them securely within controlled areas. Those areas can be locked cabinets or safes, or a dedicated media archive (GEB.8.1.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.8.2 Dust and dirt protection for archived media Staub und Schmutz
Rationale
MP-04 protects stored media until they're destroyed or sanitised. PE-14 maintains environmental conditions at levels the organisation sets, which can include limits on dust.
Gaps
GS++ asks for measures that protect archived media from dust and dirt, such as dust-tight cabinets and dry cleaning. Add them to your archive procedures.
GEB.8.3 Protection of storage media from fire damage Schutz der Datenträger vor Brandschäden
Rationale
CP-09(03) keeps backups of critical information in a fire-rated container. MP-04 stores all media securely within controlled areas, such as a media archive.
Gaps
GS++ asks for fire-resistant containers certified to a recognised standard, such as EN 1047-1 or ISO 11799. Choose data safes or fire-resistant cabinets with that certification.
GEB.8.4 Monitoring media-friendly temperature and humidity Überwachung schonender Klimatisierung 90%
Rationale
PE-14 keeps temperature and humidity within levels the organisation sets and monitors them. PE-14(02) raises an alarm when a change could harm equipment, such as stored media.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.9.1 Standard-compliant power supply Normgerechte Stromversorgung
Rationale
PE-09 protects power equipment and cabling from damage, and PE-09(01) adds redundant cabling. PE-11 provides an uninterruptible power supply that bridges an outage for a set time (GEB.9.1.3). PE-11(01) and (02) add a long-term alternate power supply (GEB.9.1.4).
Gaps
GS++ asks for power supply and cabling built to electrical standards, such as DIN VDE 0100. It also asks for a regular forward-looking load analysis (GEB.9.1.1) and a dedicated sub-distribution board fed straight from the main low-voltage distribution (GEB.9.1.2).
GEB.9.2 Load test of the power supply Lasttest 40%
Rationale
PE-11 provides the uninterruptible power supply and the alternate power source, such as a generator. These are the systems whose capacity a load test checks.
Gaps
GS++ asks for regular load tests of the uninterruptible power supply (UPS) and generators. Examples are a monthly UPS self-test and a full-load generator run of at least 30 minutes every six months.
Mapped Controls
GEB.9.3 Emergency shutoff for utilities Notaus 90%
Rationale
PE-10 lets staff cut the power in an emergency. It places the shutoff switches where authorised staff can reach them and protects them against unauthorised activation.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
GEB.9.4 Surge protection Überspannungsschutz
Rationale
PE-09 protects power equipment and cabling from damage. PE-09(02) adds automatic voltage controls for critical system components. PE-21 protects against electromagnetic pulses with measures such as surge suppressors and earthing.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.9.5 Structured data cabling Strukturierte Datenverkabelung 50%
Rationale
PE-04 controls physical access to data cabling inside the facility. It protects the cable routes, for example with conduit or locked wiring closets (GEB.9.5.1).
Gaps
GS++ asks for structured data cabling built to recognised standards, such as EN 50173 and EN 50174. Use those standards when you plan or extend the cabling.
Mapped Controls
GEB.9.6 Access to technical infrastructure rooms Zugang zu Räumen für technische Infrastruktur
Rationale
PE-02(01) authorises physical access by position or role, so only the staff who run the infrastructure get in. PE-03(01) enforces those authorisations at the entrance to each technical infrastructure room.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
GEB.9.7 Other uses of technical infrastructure rooms Zweckentfremdung 35%
Rationale
PE-18 positions system components to minimise damage from hazards and the chance of unauthorised access. Using a technical room as an office or a store room would raise both risks.
Gaps
GS++ asks you to use technical infrastructure rooms for their technical purpose alone. Write the ban on other uses into your building rules.
Mapped Controls
GEB.10.1 Climate control Klimatisierung 75%
Rationale
PE-14 keeps temperature and humidity within levels the organisation sets and monitors them (GEB.10.1.2). PE-14(01) adds automatic environmental controls, and PE-14(02) raises an alarm on changes that could cause harm.
Gaps
GS++ asks for a regular airflow analysis to check the cooling needs of server rooms (GEB.10.1.1). It also asks for redundant climate control systems (GEB.10.1.3).
Mapped Controls
GEB.10.2 Fire protection Brandschutz 60%
Rationale
PE-13 provides fire detection and suppression systems. PE-13(01) and (02) make detection and suppression start automatically (GEB.10.2.5 and GEB.10.2.6). PE-13(04) adds fire protection inspections at a set frequency (GEB.10.2.7).
Gaps
GS++ asks for structural fire protection and fire compartments to the relevant standards (GEB.10.2.1 and GEB.10.2.2). It also asks for smoke-tight rooms and materials that resist fire for a set time (GEB.10.2.3 and GEB.10.2.4).
Mapped Controls
GEB.10.3 Protection against water damage Wasserschutz
Rationale
PE-15 protects the system from water leakage, for example with shutoff valves. PE-15(01) detects water near the system (GEB.10.3.2). PE-18 positions components away from water hazards, such as rooms at risk of flooding.
Gaps
GS++ asks for at least one physical barrier against water, built to the relevant standards, between assets and each weather or water hazard. GEB.10.3.1 raises that to two structural barriers.
GEB.10.4 Lightning protection systems Blitzschutzeinrichtungen
Rationale
PE-21 protects against electromagnetic pulses, including natural ones such as lightning, with earthing and surge suppression. PE-09 protects power equipment and cabling from damage.
Gaps
GS++ asks for lightning protection systems built to a recognised standard. It also asks for regular checks that their resistance stays low (GEB.10.4.1).
GEB.10.5 Static-dissipative floor covering Ableitfähiger Fußbodenbelag 15%
Rationale
PE-14 maintains environmental conditions within levels the organisation sets. Those conditions can include static charge, which a dissipative floor drains away to earth.
Gaps
GS++ asks for a static-dissipative floor covering close to the systems in technical infrastructure rooms. Lay it to a standard such as EN 14041 or IEC 61340-4-1.
Mapped Controls
SENS.1.1 Awareness: procedures and rules Verfahren und Regelungen
Rationale
AT-01 sets and documents awareness and training policy and procedures. It assigns roles and responsibilities, shares the procedures with the people who need them and names an official to manage them. AT-02 sets the awareness training for all users that the procedures govern. AT-03 adds role-based training, which makes the training role-specific.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.1.2 Measuring the success of awareness Erfolgsmessung
Rationale
AT-02 tests what users know, and AT-02(01) uses practical exercises, such as simulated phishing, to test how they act. AT-04 documents and monitors training activities, which shows how far the training reaches. AT-06 feeds training results back to defined staff at a set frequency. PM-06 develops, monitors and reports security measures of performance, which can include awareness metrics.
Gaps
GS++ asks for regular checks of awareness success against objective criteria, covering what users know and what they do in practice. Define those criteria yourself and review the results against them.
SENS.2.1 Awareness of the protection goals Schutzziele 80%
Rationale
AT-02 gives all users literacy training on the need for security. That need includes the protection goals of availability, confidentiality and integrity, which belong at the core of the content.
Gaps
GS++ names availability, confidentiality and integrity as training topics. SP 800-53 lets you choose the topics, so cover each goal by name.
Mapped Controls
SENS.2.2 Reporting channels and information sources Meldewege
Rationale
AT-02 teaches users how to respond to suspected incidents and where to report them. IR-06 has staff report suspected incidents to the incident response team, which fixes the reporting channel. IR-07 provides a support resource, such as a help desk, that advises users on handling and reporting incidents.
Gaps
GS++ also asks users to know where to find answers to general security questions, such as the intranet or handbooks. Point users to those sources in your awareness training.
SENS.2.3 Using encryption and signature functions Verschlüsselung und Signatur
Rationale
AT-02 lets the organisation set its awareness content, which can cover the encryption and signature functions of applications. SA-05 has the user documentation describe the security functions available to users and how to use them effectively.
Gaps
GS++ asks for training on encryption and signature functions, such as signing an email or checking a messenger's end-to-end encryption. Add these to your awareness content by name.
SENS.2.4 Use of unauthorised assets Nutzung unautorisierter Assets
Rationale
PL-04 bans unauthorised assets in rules of behaviour that users acknowledge, and AT-02 carries the ban to users. AC-20 and AC-20(03) restrict or prohibit external systems, such as private devices and unapproved cloud services. CM-07(09) bans the use or connection of unauthorised hardware (SENS.2.4.1). CM-11 sets and enforces the rules on what software users may install. MP-07 restricts media types and portable storage with an unknown owner.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.2.5 Areas of responsibility and their protection needs Zuständigkeitsbereiche
Rationale
AT-02 bases awareness content on the systems users can access and their work environment. AT-03 gives role-based training on the security requirements of each person's duties and the systems in their area of responsibility.
Gaps
GS++ asks for each user to learn the protection needs of their own area and of its interfaces with other areas. Add both to the training for each role.
SENS.2.6 Bypassing security functions Umgehung von Sicherheitsfunktionen
Rationale
AT-02 teaches the user actions that keep systems secure, such as leaving safeguards in place. PL-04 sets rules of behaviour that forbid users to disable or bypass security functions.
Gaps
GS++ names bypassing security functions as a training topic, such as switching off antivirus software. Cover it by name in your awareness content.
SENS.2.7 Changing security configurations Änderung von Konfigurationen
Rationale
AT-02 teaches the user actions that keep systems secure and can explain the risk of changing security settings. PL-04 sets rules of behaviour that forbid unauthorised changes to security-relevant configurations.
Gaps
GS++ names unauthorised changes to security settings, such as firewall rules or user rights, as a training topic. Cover them by name in your awareness content.
SENS.2.8 Reporting security events Melden von Ereignissen
Rationale
AT-02 covers how users respond to suspected incidents, and AT-02(04) teaches them to recognise anomalous system behaviour, such as unexpected warnings (SENS.2.8.1). IR-06 requires staff to report suspected incidents within a set time. PL-04 makes reporting an instruction in rules of behaviour that users acknowledge.
Gaps
GS++ also asks users to report routine error and warning messages, beyond suspected incidents. Name those messages in your reporting instructions.
SENS.3.1 Risks of malware Schadprogramme 85%
Rationale
AT-02 gives all users awareness training on security risks. AT-02(04) teaches them to recognise suspicious communications and anomalous system behaviour using indicators of malicious code.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
SENS.3.2 Opening files in a sandbox Öffnen in der Sandbox
Rationale
SC-44 provides a detonation chamber, or sandbox, where users can open suspicious attachments and files in isolation. AT-02 training can tell users to open suspicious files only there.
Gaps
GS++ asks you to tell users to open suspicious files only in the sandbox. Add that instruction to your awareness training.
SENS.3.3 Converting suspicious files to a non-executable format Umwandeln verdächtiger Dateien 55%
Rationale
AT-02 lets the organisation set its awareness content. That content can teach users to convert suspicious files to a non-executable format before they open or use them.
Gaps
GS++ asks users to convert suspicious files, such as those from unknown sources, to a non-executable format before use. Teach the method and give users a tool to do it.
Mapped Controls
SENS.4.1 Handling personal authenticators Personengebundene Authentisierungsmittel
Rationale
AT-02 teaches users how to handle authenticators. IA-05 requires individuals to protect their authenticators. IA-05(01) sets password strength rules (SENS.4.1.3), and IA-05(18) provides password managers (SENS.4.1.4). PL-04 sets rules of behaviour that forbid sharing, reusing or writing down passwords. PL-04(01) bars the use of organisational passwords on external sites (SENS.4.1.2).
Gaps
GS++ also asks for training on entering credentials out of sight of others and on how biometric features can be forged. Add both topics to your awareness content.
SENS.4.2 Shared use of accounts Mehrfachnutzung von Zugängen
Rationale
IA-02 identifies and authenticates each user uniquely, which account sharing defeats. AC-02 sets the allowed account types, and AC-02(09) permits shared or group accounts only under defined conditions. PL-04 sets rules of behaviour that forbid sharing accounts. AT-02 explains to users why one account belongs to one person.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.4.3 Logging off after use Abmelden nach Nutzung
Rationale
AC-11 lets users lock the device before they leave it unattended, which GS++ counts as part of logging off. AC-12 ends sessions on defined triggers, and AC-12(01) gives users a way to log out. AT-02 reminds users to log off or lock their device after use.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.5.1 Structured data filing Datenablage
Rationale
AT-02 training can cover the structured filing scheme that users must follow, such as a file register or a content management system. PL-04 sets rules of behaviour that can require users to keep to that scheme.
Gaps
GS++ asks users to keep to a structured filing scheme. Design the scheme yourself, for example in a content management system, and teach it to users.
SENS.5.2 Passing on information Weitergabe von Informationen
Rationale
AC-21 helps users decide whether a sharing partner's access rights match the restrictions on the information before they share it. AT-02 training can cover the conditions for passing on information.
Gaps
GS++ asks users to know the legal and contractual conditions for passing on information, and which channel suits each group of recipients. Set those conditions out for users yourself.
SENS.5.3 Passing on contact details Weitergabe von Erreichbarkeiten
Rationale
AT-02(03) trains users on social engineering and social mining, which exploit published contact details. PL-04 sets rules of behaviour that can forbid disclosing such details, and PL-04(01) restricts posting organisational information on public websites and social media.
Gaps
GS++ asks users to keep contact details, such as phone numbers and internal extensions, from unauthorised third parties. That covers passing them on directly as well as publishing them. Name contact details in your rules of behaviour.
SENS.5.4 Residual and additional data in documents Rest- und Zusatzdaten 55%
Rationale
AT-02 training can teach users to remove hidden data before they send a document. That data includes the metadata fields and change history in office or PDF files.
Gaps
GS++ asks users to avoid or remove residual data, such as metadata and change history, before they send a document. Teach the steps for each file type you use.
Mapped Controls
SENS.5.5 Deletion at the end of retention periods Löschfristen
Rationale
AT-02 teaches users the retention periods and how to delete information when they end. PL-04 sets rules of behaviour that instruct users to delete or destroy information at the end of its retention period. SI-12 manages and retains information under the applicable rules, and SI-12(03) sets the techniques to dispose of it afterwards. MP-06 sanitises digital and paper media before disposal or reuse.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.5.6 Destroying paper documents Papiervernichtung
Rationale
AT-02 teaches users to destroy confidential documents. MP-06 sanitises or destroys media before disposal, including paper, with a strength matched to the information's classification. SI-12(03) sets the techniques for destroying information after the retention period.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.6.1 Scanning received removable media Scan angenommener Wechseldatenträger
Rationale
SI-03 scans files from external sources in real time at endpoints, including files on removable media, which meets the scan GS++ asks for. AT-02 tells users to scan the removable media they accept. PL-04 makes the scan an instruction in rules of behaviour that users acknowledge.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.6.2 Encrypting removable media Verschlüsselung
Rationale
SC-28(01) encrypts information at rest on defined media, including removable media. MP-05 protects media in transport outside controlled areas, for example by encryption. PL-04 sets rules of behaviour that require users to encrypt removable media, and AT-02 carries that instruction to them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.1 Awareness for specific target objects Spezifische Sensibilisierung
Rationale
AT-02 bases awareness content on the systems users can access and their work environment. AT-03 tailors role-based training to each group's duties and the specific systems it uses.
Gaps
GS++ asks for awareness shaped to each target group and the target objects it uses. Work out your target groups first, then tailor the content to each.
SENS.7.2 Virus scan of files from external sources Virenscan
Rationale
SI-03 scans files from external sources in real time as they are downloaded or opened. AT-02 tells users to check files from external sources, such as email or messenger attachments, before they open them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.3 Confidential data in automatic replies Automatische Antworten
Rationale
AT-02 can warn users against putting confidential details in automatic replies, and AT-02(03) covers social mining, which such replies can feed. PL-04 sets rules of behaviour that keep confidential content out of automatic replies.
Gaps
GS++ asks users to keep confidential data out of automatic replies, such as out-of-office notices. Set out in your rules what such a reply may contain.
SENS.7.4 Spam: deleting or reporting SPAM - Löschen oder Melden
Rationale
AT-02(04) trains users to recognise suspicious messages, such as spam, and to respond to them. IR-06 requires staff to report suspected incidents, and a suspicious email counts as one.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.5 Spam: not replying SPAM - Nichtbeantwortung 75%
Rationale
AT-02 gives users awareness training, and AT-02(04) teaches them to recognise suspicious email and how to respond to it. Leaving spam unanswered is part of that response.
Gaps
GS++ asks users to leave spam unanswered, since a reply confirms to the sender that the address is in use. Name this step in your awareness training.
Mapped Controls
SENS.7.6 Spam: opening links SPAM - Links
Rationale
AT-02(04) teaches users to spot suspicious links, and AT-02(01) exercises, such as simulated spear phishing, let them practise the response. PL-04 sets rules of behaviour that forbid opening links in unsolicited messages.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.7 Spam: opening attachments SPAM - Anhänge
Rationale
AT-02(04) teaches users the signs of malicious attachments, and AT-02(01) exercises simulate opening one. PL-04 sets rules of behaviour that forbid opening attachments in unsolicited messages.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.8 Recognising forged emails Gefälschte E-Mails 85%
Rationale
AT-02(04) trains users on the signs of suspicious email, such as a known sender's name with an unfamiliar address. AT-02(03) covers phishing and the impersonation of known senders.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
SENS.7.9 Active content in office documents Aktive Inhalte
Rationale
SC-18 defines acceptable mobile code. SC-18(04) blocks its automatic execution and enforces actions, such as prompting the user, before it runs. AT-02 tells users to check active content, such as macros, before they enable it.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.10 Disconnecting unneeded host-guest connections Trennen nicht benötigter Anschlüsse
Rationale
CM-07 keeps only the functions, ports and interfaces a system needs, such as a shared folder or USB pass-through between host and guest. AT-02 training can tell users of virtualisation to disconnect unneeded host-guest connections.
Gaps
GS++ names host-guest connections and asks users of virtualisation to disconnect the unneeded ones themselves. Add that task to your awareness training, alongside the CM-07 configuration.
SENS.7.11 Covert recording in video conferences Heimliche Aufzeichnung
Rationale
AT-02 can warn users against secret audio or video recording in video conferences. PL-04 sets rules of behaviour that forbid recording other participants unless they consent.
Gaps
GS++ names covert recording in video conferences as an awareness topic, including recordings analysed with AI. Cover it in your training and in your rules for video conferences.
SENS.7.12 Risks of public WLANs Öffentliche WLANs
Rationale
AC-19 sets connection requirements and guidance for mobile devices outside controlled areas, which tell users which networks to use. AT-02 bases awareness on users' work environment, such as telework, where the risks of public WLANs belong.
Gaps
GS++ names the risks of public WLANs, such as fake hotspots and intercepted traffic, as an awareness topic. Add them by name to your training for mobile users.
SENS.7.13 Risks of unencrypted WLANs Unverschlüsselte WLANs
Rationale
AC-19 sets connection requirements for mobile devices outside controlled areas, which can exclude unencrypted networks or require a VPN. AT-02 training can cover the risks of unencrypted WLANs.
Gaps
GS++ names the risks of unencrypted WLANs as an awareness topic, such as open networks protected only by a login page. Add them by name to your training for mobile users.
SENS.7.14 Use of unauthorised WLANs Unautorisierte WLANs
Rationale
AC-19 sets connection requirements that define which networks mobile devices may join outside controlled areas. PL-04 sets rules of behaviour that forbid connecting to unauthorised WLANs. AT-02 carries that ban to users.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.15 Social engineering calls Social Engineering Anrufe 90%
Rationale
AT-02(03) trains users to recognise and report social engineering, including pretexting and impersonation by phone. That covers a caller who poses as IT support or a manager to get a password.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
SENS.7.16 Voicemail PINs and similar credentials Mailbox-PIN und Co.
Rationale
IA-05 replaces default authenticators, such as a voicemail PIN, before first use. It also has individuals protect their authenticators. AT-02 tells users to set their own PIN or password for recordings, such as voicemail.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.17 Unencrypted telephone calls Unverschlüsseltes Telefonieren
Rationale
AT-02 training can tell users which channels are encrypted and suit confidential calls with which recipients. PL-04 sets rules of behaviour that keep sensitive conversations to encrypted channels.
Gaps
GS++ names unencrypted calls as an awareness topic, such as a conference where one participant dials in over the public phone network. Cover such cases by name in your training.
SENS.7.18 Mobile devices in secure areas Mobile Endgeräte in Sicherheitsbereichen
Rationale
SC-42 prohibits devices with sensors, such as cameras and microphones, in defined areas. PL-04 sets rules of behaviour that forbid carrying unauthorised devices into secure areas. AT-02 carries the ban to users.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.7.19 Unencrypted SMS or MMS Unverschlüsselte SMS oder MMS
Rationale
PL-04 sets rules of behaviour that can forbid SMS and MMS for organisational or sensitive communication. AT-02 carries the ban to users and explains that these messages usually travel unencrypted.
Gaps
GS++ names SMS and MMS as channels to avoid. Name them in your rules of behaviour and point users to encrypted messengers or VoIP instead.
SENS.7.20 Authenticating the other party in a conversation Authentifzierung von Gesprächspartnern
Rationale
AT-02(03) trains users to recognise social engineering, such as pretexting and impersonation, which checking the other party's identity defeats. AC-21 has users check that a sharing partner may receive the information, which means knowing who the partner is.
Gaps
GS++ asks users to confirm who they are talking to before they pass on information, by phone or in person. Set up that check yourself, for example a call back to a number from your own directory.
SENS.7.21 Legal uncertainty of faxes Rechtsunsicherheit von Faxen 55%
Rationale
AT-02 lets the organisation set its awareness content, so the training can cover the legal limits of documents that users send or receive by fax.
Gaps
GS++ asks users to know that a fax lacks the original handwritten signature. A fax therefore fails a legal written-form rule, such as the one in the German Civil Code. Brief users on where this matters.
Mapped Controls
SENS.7.22 Unencrypted fax lines Unverschlüsselte Faxleitungen 60%
Rationale
AT-02 lets the organisation set its awareness content, so the training can cover the risks of unauthenticated and unencrypted fax. Others can intercept or alter such a fax with ease.
Gaps
GS++ names the risks of fax as an awareness topic. Its guidance suggests announcing a fax in advance and confirming that it was sent and received. Build those steps into your fax procedure.
Mapped Controls
SENS.7.23 Geolocation on mobile devices Geolokation
Rationale
SC-42 restricts remote activation of sensors, such as GPS, and shows users when sensors are in use. AT-02 informs users about the location functions of their mobile devices.
Gaps
GS++ also asks users to know that mobile network operators can locate a device from its signal. Include that in your training, alongside the device's own location settings.
SENS.7.24 Certificate warnings Zertifikatswarnungen
Rationale
AT-02 training can cover certificate warnings as a sign of attack. PL-04 sets rules of behaviour that forbid overriding a certificate warning unless the override is authorised.
Gaps
GS++ names certificate warnings in web browsers as an awareness topic. Tell users to ask through the known reporting channels before they go on to the site.
SENS.8.1 Screen lock Screen Lock
Rationale
AC-11 has users lock the device before they leave it unattended. AT-02 gives users that instruction in awareness training, and PL-04 sets it as a rule of behaviour.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.8.2 Clean desk Clean Desk
Rationale
AT-02 tells users in awareness training to put confidential papers and media away, and PL-04 makes it a rule of behaviour. MP-04 physically controls digital and paper media and stores them securely.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.8.3 Risks of using mobile devices Risiken der Nutzung von mobilen Endgeräten
Rationale
AC-19 sets requirements and implementation guidance for mobile devices, including outside controlled areas, where users must protect the devices themselves. AT-02 builds the risks of mobile devices, and of settings such as telework, into awareness content.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.8.4 Closing doors and windows Schließen von Türen und Fenstern
Rationale
AT-02 reminds users in awareness training to lock doors and windows, and PL-04 makes locking rooms on leaving a rule of behaviour. PE-03 controls physical access at entry and exit points, which depends on locked doors.
Gaps
GS++ also has users close windows against the weather, such as rain and frost, to protect IT and other assets. Cover weather damage in the instruction as well as intruders.
SENS.8.5 Bringing in unauthorised IT systems Mitbringen von IT-Systemen
Rationale
AT-02 conveys the ban in awareness training, and PL-04 sets it as a rule of behaviour. CM-07(09) prohibits using or connecting unauthorised hardware. PE-16 authorises and controls components that enter the facility. SC-42 can bar devices with sensors, such as phones with cameras, from defined areas.
Gaps
GS++ names handing devices in at reception, or leaving them in lockers at the entrance, as one way to apply the ban. Provide such a place if you choose that route.
SENS.8.6 Escorting external visitors Begleitung Externer
Rationale
AT-02 tells staff in awareness training to escort external visitors, and PL-04 sets it as a rule of behaviour. PE-03 requires escorts for visitors and controls their activity.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.8.7 Supervising external visitors in sensitive areas Beaufsichtigung Externer
Rationale
AT-02 tells staff in awareness training to supervise external visitors in sensitive areas, and PL-04 sets it as a rule of behaviour. PE-03 controls visitor activity in defined circumstances. MA-05 has designated staff supervise maintenance personnel who lack access authorisation, such as IT service providers.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.8.8 Safekeeping of IT systems and media on site Verwahrung Intern
Rationale
AT-02 covers locking away IT systems and data media in awareness training. MP-04 has the organisation physically control media and store them securely in controlled areas.
Gaps
MP-04 covers media. GS++ asks users to lock away IT systems as well, especially in rooms that outsiders use, such as conference rooms. Apply your storage rules to devices too.
SENS.8.9 Return of assets no longer needed Rückgabe nicht mehr benötigter Assets
Rationale
AT-02 reminds users in awareness training to return assets, and PL-04 makes it a rule of behaviour. PS-04 retrieves organisational property when employment ends. PS-05 has people hand back keys, cards and other items when they move to a new role.
Gaps
GS++ asks users to hand back an asset whenever they stop needing it, such as at the end of a project. Add that case to the return rules you apply when people leave or change roles.
SENS.8.10 Avoiding fire loads near technical rooms Vermeidung von Brandlasten
Rationale
AT-02 explains the fire risk of combustible material in awareness training and conveys the ban. PL-04 makes it a rule of behaviour to keep such material away from technical rooms.
Gaps
GS++ asks users to keep combustible material, such as cardboard boxes and batteries, away from technical rooms and utilities. Set the safe distance yourself, by the size of the fire load and the room's protection needs.
SENS.8.11 Use of fire protection equipment Verwendung von Brandschutmitteln
Rationale
AT-03(01) trains defined staff to use environmental controls, including handheld fire extinguishers. PE-13 provides the fire detection and suppression equipment that staff learn to use.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.8.12 Use of water protection equipment Verwendung von Wasserschutzmitteln
Rationale
AT-03(01) trains defined staff to use environmental controls. PE-15 keeps master shutoff valves accessible and working, and makes sure key personnel know about them.
Gaps
GS++ counts simple aids, such as sandbags and water barriers, as water protection equipment. Train staff on each aid you provide, as well as on the shutoff valves.
SENS.9.1 Processing confidential information in public Verarbeitung in der Öffentlichkeit
Rationale
AT-02 covers the risk of working on confidential data in public, as part of content on telework and travel. PL-04 forbids processing confidential information where others can see or hear it. AC-19 gives guidance for mobile devices used outside controlled areas.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.9.2 Caution against eavesdropping in mobile working Vorsicht vor Mithören
Rationale
AT-02 provides awareness training, and its content can warn users about being overheard during mobile working. PE-17 sets controls for alternate work sites, such as home offices, which can include rules for confidential calls.
Gaps
GS++ names the risk of being overheard during mobile working, such as on a journey or in public, as an awareness topic. Add it to your training content and your rules for confidential calls.
SENS.9.3 Safekeeping of IT systems and media away from the office Verwahrung außer Haus
Rationale
AT-02 covers keeping devices and media safe during mobile working, and PL-04 sets rules for storing them away from the office. AC-19 notes that users must physically protect mobile devices outside controlled areas. MP-05 protects and controls media outside controlled areas.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.9.4 Mobile working with paper documents Mobile Arbeit mit Dokumenten
Rationale
AT-02 covers the handling of paper documents during mobile working in awareness training. MP-05 protects and controls non-digital media, paper included, during transport outside controlled areas.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.9.5 Taking IT systems and media to mobile working Mitnahme zur mobilen Arbeit
Rationale
AT-02 awareness content can advise users to take only the devices and media their task needs. PL-04 can limit what users take off site through the rules of behaviour.
Gaps
GS++ asks users to take only the IT systems and media they need, judged by the permitted data locations and their tasks. Set that limit yourself in your rules for mobile working.
SENS.9.6 Taking IT systems and media abroad Mitnahme ins Ausland
Rationale
AT-02 conveys the ban and the risks of foreign travel in awareness training. PL-04 can forbid taking unneeded devices and media abroad as a rule of behaviour. CM-02(07) issues specially configured devices to people travelling to high-risk locations and applies controls on their return.
Gaps
CM-02(07) provides prepared devices for travel. GS++ also asks users to take abroad only the IT systems and media the business needs. Write that limit into your travel rules.
SENS.9.7 Travel and safety advice for trips outside Europe Reise- und Sicherheitshinweise 55%
Rationale
AT-02 awareness content can point travellers to official travel and safety advice. AT-02(06) brings the current threat environment into training, which can include the risks of the destination country.
Gaps
GS++ asks users to check the German Federal Foreign Office's travel and safety advice before trips outside Europe. Point travellers to that source in your awareness content.
Mapped Controls
SENS.10.1 Basic principles of system administration Grundprinzipien der Systemadministration 80%
Rationale
AT-03 gives role-based training to people in administrator roles, matched to their duties. For system and network administrators, that training covers the principles of secure administration.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
SENS.10.2 Handling privileged access rights Umgang mit privilegierten Berechtigungen
Rationale
AT-03 trains administrators in the use of privileged rights, and PL-04 sets separate rules of behaviour for privileged users. AC-06(02) has privileged users switch to non-privileged accounts for non-security tasks. IA-05 protects authenticators, and IA-05(07) keeps unencrypted credentials out of scripts and applications.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.10.3 System administration: security incidents Systemadministration - Sicherheitsvorfälle
Rationale
AT-03 gives administrators role-based training on the incident procedures and their duties in an incident. IR-02 gives incident response training that matches each person's assigned roles and responsibilities.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.10.4 System administration: structured cabling Systemadministration - Strukturierte Verkabelung
Rationale
AT-03 gives network administrators role-based training, which can cover structured cabling. PE-04 protects distribution and transmission lines, for example with conduits and locked wiring closets, and structured cabling supports that protection.
Gaps
GS++ asks for awareness of structured cabling, where cable routes and connections follow one documented plan. Base the training on a cabling standard, such as EN 50173, and on your own labelling scheme.
SENS.10.5 System administration: internet use Systemadministration - Internetnutzung
Rationale
AC-06(02) has administrators use non-privileged accounts for non-security tasks, such as web browsing. AT-03 trains administrators on the risk of browsing with administrator rights. PL-04 forbids internet access from administrator accounts in the rules for privileged users.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.11.1 Awareness for top management Sensibilisierung der Institutionsleitung
Rationale
AT-02 includes managers and senior executives in literacy training and awareness, which covers the need for security. AT-03 gives senior leaders role-based training on their security responsibilities.
Gaps
GS++ asks for top management to learn why information security matters for protecting business processes. Build that link into the training content for senior leaders.
SENS.11.2 Leading by example Führen als Vorbild
Rationale
AT-02 includes managers in literacy training and awareness, alongside other staff. AT-03 gives managers role-based training on their responsibilities, and that training can cover leading by example.
Gaps
GS++ asks for managers to learn that they set the example for information security, so staff apply their training in daily work. Add that role-model duty to managers' training.
SENS.11.3 Whaling attacks on executives Whaling
Rationale
AT-02(03) trains users, executives included, to recognise social engineering such as phishing and impersonation. AT-02(05) covers advanced persistent threats, which can target executives. AT-03(03) runs practical exercises that include whale phishing aimed at senior leaders.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
SENS.12.1 High risks from the risk analysis Hohe Risiken
Rationale
AT-02(06) brings current threat information into literacy training and awareness. RA-03 shares the results of the risk assessment, including the high risks it finds, with defined personnel.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.1.1 Architecture: procedures and rules Verfahren und Regelungen
Rationale
SC-01 sets system and communications protection policy and procedures and names an official to manage them. It documents them and gives them to the roles that need them. PL-08 describes the security architecture, including how the network and connected infrastructure are protected.
Gaps
GS++ asks for procedures and rules for the network architecture in particular. SC-01 covers system and communications protection as a whole, so give network architecture its own section in those procedures.
ARCH.1.2 Architecture: regular review Regelmäßige Überprüfung
Rationale
SC-01 has the organisation review and update its system and communications protection policy and procedures at a set frequency and after defined events. PL-08 reviews and updates the security architecture at a set frequency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.2.1 Network segments Netzsegmente
Rationale
PL-08 sets the segmentation approach in the security architecture. SC-07 controls traffic at key internal interfaces, and SC-07(21) and (29) isolate components and functions in separate subnetworks. SC-32 partitions the system into separate physical or logical domains according to defined circumstances, such as protection needs.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.2.2 Restricting connections between segments Einschränkung von Verbindungen zwischen Segmenten
Rationale
AC-04 enforces approved information flows between segments. SC-07 controls traffic at internal interfaces and puts public services in a DMZ. SC-07(05) denies traffic by default. SC-07(13) isolates management systems and SC-07(15) routes privileged access through jump servers. SC-07(21) and (29) place components in separate subnetworks. SC-32 partitions groups such as operational technology (OT) and test systems into separate domains. CA-09 authorises internal connections, such as printers and OT systems. PE-04 controls physical access to network lines (ARCH.2.2.11).
Gaps
GS++ names specific separations, including IPv4 from IPv6 and, as an option, VoIP from data systems (ARCH.2.2.9, ARCH.2.2.4). Add them to the flow rules at your segment boundaries.
ARCH.2.3 Microsegmentation Mikrosegmentierung
Rationale
AC-04 enforces the allowed information flows for each system and limits which other systems it may talk to. SC-07(12) puts boundary protection, such as a firewall, on each host, and SC-07(21) isolates components from each other.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.2.4 Inventory of networks Inventar der Netze
Rationale
CA-03 documents each external connection and its interface. CA-09 does the same for internal connections and the information they carry. CM-08 inventories system components, including network devices. PL-02 describes the connections to other systems and the operating environment in the security plan.
Gaps
GS++ asks for one inventory of networks, listing internal segments and external connections with the purpose of each. Bring the details these controls record together in that inventory.
ARCH.2.5 Network diagram Netzplan
Rationale
CM-02 records the network topology and where components sit in the baseline configuration. PL-02 describes the system components and connections to other systems in the security plan. PL-08 describes how the network is arranged and protected in the security architecture.
Gaps
GS++ asks for a network diagram that shows the logical and physical structure of the network. Draw it from the topology and connections these controls record, and keep it up to date.
ARCH.2.6 Network topology monitoring Topologieüberwachung
Rationale
CA-07 assesses controls on an ongoing basis at a set frequency, which can include the network architecture. CM-08(03) detects unauthorised components on the network. SI-04 detects unauthorised connections to the system, and SI-04(14) finds rogue wireless devices.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.3.1 WLAN coverage Netzabdeckung 45%
Rationale
AC-18(05) has the organisation choose antennas and set transmit power so the wireless signal stays within its controlled boundaries. This limits who can pick up the network from outside.
Gaps
GS++ asks you to test WLAN coverage, so the signal reaches the places where people need it. Test reception at key locations under real conditions.
Mapped Controls
ARCH.3.2 Restricting WLAN signals in secure areas Einschränkung in Sicherheitsbereichen
Rationale
AC-18(05) chooses antennas and sets transmit power so wireless signals stay within defined areas. PE-19 protects against information leaking out through electromagnetic signals, for example by shielding rooms.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.3.3 Organisation-specific WLAN names (SSIDs) SSIDs
Rationale
AC-18 sets configuration requirements for each type of wireless access. CM-06 sets secure configuration settings that replace vendor defaults, such as the factory network name (SSID).
Gaps
GS++ asks for WLAN names specific to the organisation, so users can recognise its networks and tell them apart. Choose descriptive names, such as one that marks the guest network.
ARCH.3.4 Encrypted WLAN connections Verschlüsselte Netzanbindung
Rationale
AC-18(01) protects wireless access with authentication and encryption. SC-08(01) encrypts information in transit, and SC-08(03) also protects data outside the message content, such as addresses. SC-13 sets the type of cryptography for each use, so you can require a recognised standard.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.4.1 Network access control Netzzugangskontrolle
Rationale
IA-03 identifies and authenticates devices before they connect to the network, and IA-03(04) bases this on device attestation. CA-09(01) checks components for compliance before an internal connection, as dynamic network access control does (ARCH.4.1.1). CM-08(03) disables network access for unauthorised components or isolates them. SC-07(20) isolates components dynamically, as a quarantine network does (ARCH.4.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.4.2 Authorised routing Autorisiertes Routing
Rationale
CM-03 reviews and approves configuration changes, such as new routes, under change control. CM-05 restricts who may change router configurations. AC-04 enforces approved authorisations for information flows between connected systems.
Gaps
GS++ asks a responsible person or role to authorise each routing connection. Assign that role and send routing changes to it for approval.
ARCH.4.3 Authentication of routing protocols Authentifizierung von Routingprotokollen
Rationale
IA-03(01) authenticates routing peers with cryptography before they connect. SC-08 protects routing updates in transit, and SC-08(01) detects any change to them. SC-23 protects the authenticity of routing protocol sessions.
Gaps
GS++ gives route origin validation with RPKI as an example, which protects BGP against route hijacking. Add origin validation alongside the peer authentication these controls cover.
ARCH.5.1 Restricting and inspecting connections Einschränkung und Inspektion von Verbindungen
Rationale
AC-04(08) filters content, such as web and DNS traffic. AC-04(04) controls encrypted traffic and AC-04(03) adapts flow rules to changing conditions. CM-07 blocks vulnerable protocols and services, including dynamic routing at the edge. SC-07 denies traffic by default, prevents split tunnelling, routes traffic through proxies and checks protocol formats. SI-03 stops known malicious content at network entry points. SI-04(04) watches traffic in and out for attacks, and SI-04(10) makes encrypted traffic visible. PL-08(01) layers the filters, as P-A-P does, and PL-08(02) takes them from different suppliers.
Gaps
GS++ asks for the P-A-P structure, two packet filters with an application gateway between them, each on separate hardware. It also asks you to block known illegal content and layer 2 attacks, for example with DHCP snooping.
ARCH.5.2 Blocking direct connections to public networks Blockieren direkter öffentlicher Verbindungen 95%
Rationale
SC-07 connects the system to external networks only through managed interfaces, which filter the traffic. SC-07(28) prohibits direct connection of the systems you define to a public network.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ARCH.6.1 Controlled paths for wide area connections Kontrollierte Verbindungsführung
Rationale
AC-04(21) separates information flows physically or logically. SC-07(04) gives each external telecommunication service a managed interface and a traffic flow policy. SC-08(05) protects transmission lines with a protected distribution system, which controls the physical path.
Gaps
GS++ names dedicated routes, such as dark fibre, as one way to control the path physically. Use dedicated lines where a link needs that level of control.
ARCH.6.2 Encryption of wide area connections Verschlüsselung von Weiterverkehrsverbindungen
Rationale
SC-08(01) encrypts information in transit, such as traffic over wide area links. AC-17(02) encrypts remote access sessions. SC-13 sets the type of cryptography for each use, so you can require a recognised standard.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.7.1 Dedicated host systems for servers Dedizierte Hostsysteme für Server
Rationale
CM-07 configures systems to provide only essential capabilities, and SP 800-53 advises one function per component where feasible. SC-32 partitions components into separate physical or logical domains, which can mean a dedicated virtual or physical host for each application.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
ARCH.7.2 Dedicated hardware for host systems Dedizierte Hardware 65%
Rationale
SC-32 partitions system components into separate physical domains. Choosing physical separation puts host systems on dedicated hardware of their own.
Gaps
GS++ aims to avoid circular dependencies, such as a virtualisation host whose domain controller runs as a virtual machine on that same host. Run the services a host depends on elsewhere.
Mapped Controls
ARCH.7.3 Separating development and test environments Entwicklungs- und Testumgebungen
Rationale
CM-04(01) analyses changes in a separate test environment before they go into operation. SC-32 partitions development and test systems from production into separate domains.
Gaps
GS++ asks for development and test environments on hosts of their own, apart from production hosts. A fault in test software then stays away from the production hypervisor.
ARCH.8.1 Redundancy in the core network Redundanz im Kernnetz 55%
Rationale
SI-13 provides standby components and a way to swap them in when an active component fails. SI-13(05) adds failover, so the switch happens in real time or near real time.
Gaps
GS++ asks for redundant components in the core network, so the network stays up when one of them fails. Give each critical core device a standby.
Mapped Controls
ARCH.8.2 Redundant telephony connections Redundante TK-Anbindung 85%
Rationale
CP-08 sets up alternate telecommunications services that can take over when the primary service fails. CP-08(02) avoids a single point of failure shared with the primary service, and CP-08(03) gets the alternate service from a separate provider.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
ARCH.8.3 Redundant servers Redundante Server
Rationale
SI-13(05) provides failover to standby components in real time or near real time. CP-09(06) keeps a redundant secondary system ready to take over without loss of information. SC-36 distributes processing and storage across several locations or domains.
Gaps
GS++ counts a host as redundant when its power supply and network connection are redundant too. Build both into each host the application needs.
ARCH.9.1 Sizing the network connection Dimensionierung der Netzanbindung
Rationale
CP-02(02) plans the processing and telecommunications capacity needed during contingency operations. SC-05(02) manages capacity and bandwidth so services withstand flooding attacks.
Gaps
GS++ asks you to size network connections to the organisation's normal demand. Record what critical processes need and plan link capacity from that.
ARCH.9.2 Load balancing Lastverteilung
Rationale
SC-05(02) manages capacity and redundancy so services stay available under heavy load. SC-36 distributes processing across several components or domains, so many systems share the work.
Gaps
GS++ suggests automatic load balancing, run by the network or by the servers themselves. Choose the method that suits each application, such as a load balancer in front of several servers.
ARCH.9.3 Automatic scaling Automatische Skalierung 40%
Rationale
SC-05(02) manages the capacity of the system to limit the effects of flooding and overload. That keeps the application available when demand rises.
Gaps
GS++ suggests scaling an application's instances up and down automatically, based on thresholds such as CPU load or response time. Set those thresholds for each application.
Mapped Controls
ARCH.9.4 Content delivery network Content Delivery Network
Rationale
SC-05 limits the effects of denial-of-service attacks, and SC-05(02) adds capacity and redundancy against flooding. SC-36 distributes processing and storage across physical locations, as a content delivery network does.
Gaps
GS++ suggests a content delivery network for applications that must stay available worldwide, to absorb load peaks and denial-of-service attacks. You can run one yourself or use a service provider.
ARCH.9.5 Protection against volumetric denial-of-service attacks Schutz gegen volumetrische DoS-Angriffe 90%
Rationale
SC-05 protects against denial-of-service attacks or limits their effects, using controls the organisation chooses. SC-05(02) manages capacity and bandwidth to absorb floods, and SC-05(03) detects and monitors attacks.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.1.1 Access rights: procedures and rules Verfahren und Regelungen
Rationale
AC-01 sets access control policy and procedures, documents them, gives them to the roles that need them and names an official to manage them. The policy covers the management of accounts and access rights. IA-01 does the same for identification and authentication, which covers the identity side.
Gaps
GS++ asks for each identity and access management task to go to a named person or role. SP 800-53 sets roles and responsibilities at the level of the policy, so assign the tasks yourself.
BER.1.2 Access rights: regular review Regelmäßige Überprüfung
Rationale
AC-01 has the organisation review and update its access control policy and procedures at a set frequency and after defined events. IA-01 does the same for the identification and authentication policy and procedures.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.1.3 Inventory of authentication and authorisation systems Inventar Authentifizierungs- und Autorisierungssysteme 60%
Rationale
CM-08 keeps an inventory of system components, which can list each authentication and authorisation system, such as directory services, identity providers and single sign-on platforms. CM-08(04) records who is responsible for each component.
Gaps
CM-08 asks for an inventory of all components. GS++ asks for a separate view of the authentication and authorisation systems, so mark them in the inventory with their protocols and connected applications.
Mapped Controls
BER.1.4 Inventory of access rights Inventar der Berechtigungen
Rationale
AC-02 specifies, for each account, its authorised users, its group and role memberships and its access authorisations. That is the core of an access rights inventory. IA-04 assigns each identifier to the intended person, role, service or device, which links people to their identities.
Gaps
GS++ asks for one inventory across all systems that links people, identities, accounts and access rights. AC-02 works system by system, so bring the account records together into that inventory yourself.
BER.2.1 Identity linked to one person or IT system Person-Identität
Rationale
IA-02 uniquely identifies each of the organisation's users and ties that identity to the processes acting for them. IA-03 uniquely identifies devices, which covers the identities of IT systems. IA-04 assigns each identifier to the one person, service or device it is meant for. IA-12 resolves each user identity to a unique individual through identity proofing.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.2.2 Restricting who can manage identities Einschränkung
Rationale
AC-06 applies least privilege, and AC-06(01) lets only defined roles use security functions such as identity administration. IA-04 requires authorisation from defined roles before an identifier is assigned. IA-04(09) keeps identity attributes in protected central storage.
Gaps
SP 800-53 asks for authorisation before an identifier is assigned. GS++ also restricts who may change or delete an identity. Give write access to identity records to named roles alone, such as HR or the administrators.
BER.2.3 Checking identity master data Stammdatenprüfung
Rationale
AC-02 reviews accounts at a set frequency. It also aligns account management with the personnel processes for leaving and transfers, which ties account data to HR records. SI-18 checks personal data at a set frequency for accuracy and completeness, and corrects it. This covers the master data of people's identities.
Gaps
GS++ asks you to check identity master data regularly against source records, such as HR files, network scans or a configuration management database. SI-18 covers personal data, so set up the same check for IT-system identities.
BER.2.4 Logging changes to identity master data Protokollierung von Stammdatenänderungen
Rationale
AC-02(04) automatically audits when accounts are created, changed, enabled, disabled or removed, which covers identity data held in accounts. AU-02 lets the organisation name changes to identity master data as an event type to log. AU-03 makes each record show what happened, when and which account acted. AU-12 generates the records for those event types.
Gaps
AC-02(04) logs changes to accounts. GS++ also covers identity master data held outside accounts. Add changes to that data to the event types you log under AU-02.
BER.2.5 Deactivation of identities on leaving Deaktivierung bei Weggang
Rationale
AC-02 tells account managers when users leave and disables their accounts in step with the termination process. AC-02(03) disables accounts that have lost their link to a user or have been inactive for a set period. PS-04 disables system access within a set time when someone leaves and revokes their authenticators and credentials.
Gaps
GS++ counts long absences, such as parental leave or a sabbatical, as leaving. PS-04 covers the end of employment, so add long absences to the conditions under which AC-02 disables accounts.
BER.2.6 Deletion of identities after the retention period Löschen nach Fristablauf
Rationale
AC-02 removes unneeded accounts in line with defined policy and criteria. SI-12 keeps information for as long as laws and policy require, and SI-12(03) disposes of it when the retention period ends.
Gaps
AC-02 removes accounts. GS++ also asks you to delete identity records securely when their retention period ends. Choose disposal methods under SI-12(03) that also reach copies in backups.
BER.3.1 Central management of accounts Zentrales Management
Rationale
AC-02(01) supports account management with automated mechanisms. IA-13 uses identity providers and authorisation servers to manage identities and their access rights centrally. PL-09 lets the organisation manage chosen controls, such as account management, centrally across systems.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.2 Authorisation of new accounts Autorisierung neuer Zugangskonten
Rationale
AC-02 requires defined people or roles to approve each request to create an account. IA-04 requires authorisation from defined roles before an account identifier is assigned.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.3 Restricting account management to administrators Einschränkung des Managements
Rationale
AC-02 assigns account managers, so only designated staff manage accounts. AC-06(01) lets only defined roles use security functions such as account management, and AC-06(05) restricts privileged accounts to defined personnel.
Gaps
GS++ limits account management to administrators. AC-02 lets you choose the account managers, so give that role to administrators.
BER.3.4 Logging changes to accounts Protokollierung von Änderungen
Rationale
AC-02(04) automatically audits when accounts are created, changed, enabled, disabled or removed. AU-02 has the organisation select these account actions as event types to log, and AU-12 generates the records. AU-09 protects the records from unauthorised change and deletion, so the log stands up to audit.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.5 Account linked to one identity Identität-Zugangskonto
Rationale
AC-02 names the authorised user of each account. IA-02 uniquely identifies each of the organisation's users, so every account traces back to one person. IA-04 assigns each account identifier to the one holder it is meant for.
Gaps
AC-02(09) allows shared and group accounts under defined conditions. GS++ asks for each account to belong to exactly one identity, so make that your rule.
BER.3.6 Privileged accounts Privilegierte Zugangskonten
Rationale
AC-02(07) sets up and administers privileged accounts under a role-based scheme. AC-06(02) has users with privileged access use non-privileged accounts for other work, such as email and web browsing. So administrators use separate accounts for administration.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.7 Single sign-on Single-Sign-On
Rationale
IA-02(10) provides single sign-on for defined accounts and services. IA-13 has applications rely on central identity providers and authorisation servers to authenticate users and authorise their access.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.8 Account hints in login error messages Hinweise bei Anmeldefehlern
Rationale
IA-06 obscures the feedback from authentication, so the message after a failed login hides details such as whether the account exists. SI-11 keeps error messages free of information an attacker could exploit.
Gaps
GS++ names user enumeration, where an attacker probes which accounts exist. Give the same message for a wrong user name as for a wrong password.
BER.3.9 Event-driven deactivation of accounts Ereignisgesteuerte Deaktivierung
Rationale
AC-02(03) disables accounts that have expired, have lost their link to a user, breach policy or have been inactive for a set period. AC-02(13) disables the accounts of high-risk individuals. PS-04 disables system access when employment ends.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.10 Login attempt limit on IT systems Anmeldeversuchsgrenze am System 95%
Rationale
AC-07 limits the number of consecutive failed login attempts. Once the limit is reached, it locks the account or device for a set time or delays the next login prompt.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.3.11 Login attempt limit for applications Anmeldeversuchsgrenze an der Anwendung 95%
Rationale
AC-07 limits the number of consecutive failed login attempts, in applications as well as on systems. Once the limit is reached, it locks the account for a set time or delays the next login prompt.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.3.12 System lock after inactivity Systemsperre bei Inaktivität
Rationale
AC-11 locks the device after a set period of inactivity and keeps it locked until the user signs in again. AC-12 ends the session after defined conditions, such as inactivity, which covers the logout that GS++ accepts in place of a screen lock.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.13 Application lock after inactivity Sperre der Anwendung bei Inaktivität
Rationale
AC-11 locks access after a set period of inactivity until the user authenticates again, and the same rule can apply to an application. AC-12 ends a user's session automatically after defined conditions, such as inactivity. IA-11 asks the user to authenticate again in defined situations, such as returning to an idle application session.
Gaps
SP 800-53 sets the inactivity lock at device level. In each application, build the lock from AC-12 session termination or an IA-11 prompt to sign in again.
BER.3.14 Blocking the reuse of accounts Kein Recycling von Zugängen 90%
Rationale
IA-04 blocks the reuse of identifiers for a defined period. That stops a former account from passing to another person, role, service or device within that time.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.3.15 Deletion of accounts after the retention period Zugang löschen nach Fristablauf
Rationale
AC-02 removes unneeded accounts in line with defined policy and criteria. SI-12 sets how long information is held, and SI-12(03) disposes of it when the retention period ends. Account records follow the same timing.
Gaps
GS++ ties account deletion to the legal retention periods and asks for secure deletion, including copies in backups. Apply the SI-12 retention periods to account records and choose disposal methods that reach backups.
BER.3.16 Banning shared accounts Keine Gruppenkonten
Rationale
AC-02 defines the allowed and the prohibited account types, so shared accounts can go on the prohibited list. AC-02(09) allows shared and group accounts only under defined conditions. IA-02 requires each of the organisation's users to be uniquely identified, which calls for individual accounts.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.17 Shared accounts: multi-factor authentication Gruppenkonten - MFA 85%
Rationale
IA-02(01) and (02) require multi-factor authentication for privileged and non-privileged accounts. Every account falls into one of those two types, so they cover shared accounts too.
Gaps
SP 800-53 sets multi-factor authentication by account type. GS++ names shared accounts. Turn it on for each shared account, for example with several hardware tokens or one-time password apps registered to it.
Mapped Controls
BER.3.18 Shared accounts: documenting handovers Gruppenkonten - Wechsel dokumentieren
Rationale
AC-02 specifies the authorised users and group membership of each account, which records who may use a shared account. IA-02(05) has each user authenticate individually before using a shared account, which records who used it and when.
Gaps
AC-02 lists who may use an account. GS++ also asks for a record of who could use a shared account at each handover, such as a shift change. Duty rosters can serve as that record.
BER.3.19 Shared accounts: password change on leaving Gruppenkonten - Passwortwechsel bei Weggang
Rationale
AC-02 changes the authenticators of shared or group accounts when someone leaves the group. IA-05 changes the authenticators of group or role accounts whenever their membership changes.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.3.20 Caching of login credentials Zwischenspeicherung von Zugangsdaten 70%
Rationale
IA-05(13) stops cached authenticators from working after a set period. IA-05 also protects the content of authenticators from disclosure, which makes them harder to steal.
Gaps
GS++ asks you to turn off credential caching on IT systems. IA-05(13) limits how long cached authenticators work, so set that period to zero.
Mapped Controls
BER.3.21 Service accounts Dienstekonten
Rationale
IA-05 refreshes authenticators on a schedule or after defined events. IA-05(07) keeps unencrypted static credentials out of code and storage, and IA-05(18) uses password managers to generate and manage passwords. SC-12 manages the keys and certificates that service accounts use to authenticate.
Gaps
GS++ asks for automatic rotation and distribution of service account credentials, free of manual steps. Automate the IA-05 refresh for these accounts, for example with a secrets vault.
BER.3.22 Emergency access accounts Notfallzugang
Rationale
AC-02 defines emergency accounts as an account type, and AC-02(02) disables or removes them automatically after a set period. AC-03(10) lets defined roles override access controls under defined conditions, with an audit trail, which is the break-glass case.
Gaps
SP 800-53 treats emergency accounts as short-lived accounts for a crisis. GS++ describes a standing break-glass account, set up in advance. Give it a long password and store it in a safe or split it between administrators.
BER.3.23 Emergency access account for directory services Notfallzugang Verzeichnisdienst
Rationale
AC-02 defines emergency accounts as an account type, which can include one for the directory service. AC-02(02) disables or removes emergency accounts automatically after a set period. AC-03(10) lets defined roles override access controls under defined conditions, with an audit trail, which covers emergency access to the directory.
Gaps
SP 800-53 treats emergency accounts as short-lived accounts for a crisis. GS++ asks for a standing break-glass account for each directory service, set up in advance. Give it a long password and store it in a safe or split it between administrators.
BER.3.24 Alternative authentication on IT systems Alternative Authentifizierung am IT-System
Rationale
AC-07(04) allows an alternate authentication factor, different from the primary one, once the login attempt limit is reached. IA-05 sets procedures for lost or damaged authenticators and requires each authenticator to be strong enough for its use.
Gaps
GS++ asks for the alternative method to be as trustworthy as the primary one. IA-05 asks for sufficient strength, so give the recovery path the same assurance as the normal login.
BER.3.25 Alternative authentication for applications Alternative Authentifizierung an der Anwendung
Rationale
AC-07(04) allows an alternate authentication factor, different from the primary one, once the login attempt limit is reached. IA-05 sets procedures for lost or damaged authenticators in applications and requires each authenticator to be strong enough for its use.
Gaps
GS++ asks for the alternative login to an application to be as trustworthy as the primary one. IA-05 asks for sufficient strength, so give account recovery the same assurance as the normal login.
BER.4.1 Principle of least privilege Prinzip der geringsten Berechtigungen
Rationale
AC-06 gives users and processes only the access their tasks need. AC-03(07) enforces role-based access control (BER.4.1.1). AC-02(06) manages privileges dynamically for just-in-time access (BER.4.1.2), and AC-02(07) runs privileged accounts on a role-based scheme.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.4.2 Authorisation of access rights Autorisierung von Berechtigungen 85%
Rationale
AC-02 authorises access on the basis of a valid access authorisation and the intended use of the system. It requires defined roles to approve requests to create accounts and sets the criteria for group and role membership.
Gaps
AC-02 names approvers for new accounts. GS++ asks for named people or roles to authorise every assignment of access rights, so extend the approval step to later grants too.
Mapped Controls
BER.4.3 Justification of access rights Begründung von Berechtigungen 60%
Rationale
AC-02 records the access authorisations of each account and ties each one to the intended use of the system. AC-02(04) audits changes to accounts, which leaves a record of each modification.
Gaps
GS++ asks for a written reason with every grant of access rights and every change to them. Add a justification field to your access request process, for example in your identity and access management system.
Mapped Controls
BER.4.4 Review of access rights Überprüfung von Berechtigungen
Rationale
AC-02 reviews accounts at a set frequency against the account management requirements, which compares documented with actual access rights (BER.4.4.1). AC-06(07) reviews assigned privileges at a set frequency and removes unneeded ones.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.4.5 System functions without authentication Systemfunktionen ohne Authentifizierung 95%
Rationale
AC-14 identifies the user actions a system allows without identification or authentication. It documents them in the system's security plan, with the reasons for each.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.4.6 Application functions without authentication Anwendungsfunktionen ohne Authentifizierung 95%
Rationale
AC-14 identifies the user actions an application allows without identification or authentication, such as a password reset or public content. It documents them in the security plan, with the reasons for each.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.4.7 IT system linked to one account IT-System-Zugangskonto
Rationale
AC-02 specifies the authorised users of a system, which can be a single account. AC-03 enforces the approved authorisations, so only that account can reach the system.
Gaps
GS++ suggests binding an IT system that needs special protection to exactly one account. Limit the authorisations for that system to the one account yourself.
BER.4.8 Revocation of access rights Entzug von Berechtigungen
Rationale
AC-02 disables or removes accounts when the need for access ends and aligns this with personnel processes. AC-03(08) revokes access authorisations when security attributes change. PS-04 disables access and revokes credentials when employment ends. PS-05 reviews and modifies access authorisations when people move to other roles.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.5.1 Issuing, registering and assigning authenticators Ausgabe, Registrierung und Zuordnung
Rationale
IA-05 verifies the recipient's identity before it first hands out an authenticator (BER.5.1.1), and sets procedures for initial content and distribution. IA-05(02) maps each key-based identity to its account. IA-12 checks each user's identity evidence at registration, so authenticators go to the right person.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.5.2 Resetting and replacing authenticators Zurücksetzung und Ersetzung von Authentifizierungsmitteln 85%
Rationale
IA-05 sets procedures for authenticators that are lost, compromised or damaged, which covers resetting and replacing them. It also changes or refreshes authenticators when defined events occur, such as a suspected compromise.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.5.3 Procedure for revoking authenticators Vorgehensweise zum Widerruf
Rationale
IA-05 sets administrative procedures for revoking authenticators, whatever the reason. PS-04 covers people who leave the organisation and revokes their authenticators and credentials when their employment ends.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.5.4 Only established cryptography for authenticators Nur etablierte Kryptographie
Rationale
IA-05 asks for authenticators with enough strength of mechanism for their intended use. IA-05(01) stores passwords with an approved salted key derivation function. SC-13 implements the type of cryptography each use requires, authentication included.
Gaps
GS++ asks for algorithms from one or more recognised standards. Name yours, such as BSI TR-02102, where SC-13 has you set the cryptography each use requires.
BER.5.5 Disabling biometric-only authentication on IT systems Deaktivierung einfacher Biometrie auf IT-Systemen
Rationale
IA-02(01) and (02) ask for multi-factor authentication, so a biometric works only together with another factor. IA-05 asks for authenticators strong enough for their intended use. IA-05(12) sets biometric quality requirements, and IA-05(17) detects presentation attacks, such as forged fingerprints.
Gaps
GS++ asks for sign-in by biometrics alone to be switched off on IT systems, such as fingerprint unlock on a smartphone. SP 800-53 reaches this through multi-factor authentication where IA-02 asks for it, so switch biometric-only sign-in off everywhere else too.
BER.5.6 Disabling preconfigured authenticators on IT systems Vorkonfigurierte Authentisierungsmittel von IT-Systemen
Rationale
CM-06 sets secure configuration settings that disable vendor default accounts and credentials on each system. IA-05 changes default authenticators before first use, and IA-05(05) has developers and installers provide unique authenticators before delivery.
Gaps
IA-05 asks you to change default authenticators. GS++ asks you to switch them off, hardware tokens and certificates included, so cover these in your CM-06 settings.
BER.5.7 Disabling preconfigured authenticators in applications Vorkonfigurierte Authentisierungsmittel von Anwendungen
Rationale
CM-06 sets secure configuration settings that disable vendor default accounts and credentials in applications. IA-05 changes an application's default authenticators before first use, and IA-05(05) has developers and installers provide unique authenticators before delivery.
Gaps
IA-05 asks you to change an application's default authenticators. GS++ asks you to switch them off, tokens and certificates included, so cover these in your CM-06 settings.
BER.5.8 Multi-factor authentication at the perimeter Mehr-Faktor-Authentisierung am Perimeter
Rationale
IA-02(01) and (02) ask for multi-factor authentication on every account, IA-02(06) puts one factor on a separate device and IA-02(08) makes sign-in resistant to replay. AC-17 sets the connection requirements for each type of remote access, such as multi-factor authentication at the VPN gateway.
Gaps
GS++ asks for phishing-resistant methods, such as FIDO2 passkeys, on every interface reachable from outside. SP 800-53 asks for replay resistance, which covers part of that, so choose a method that resists fake login pages.
BER.5.9 Multi-factor authentication for far-reaching access rights Mehr-Faktor-Authentisierung für weitreichende Berechtigungen 90%
Rationale
IA-02(01) asks for multi-factor authentication on privileged accounts, such as administrator accounts for the directory service or DNS. IA-02(02) extends it to other accounts, which covers wide access to sensitive data.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.5.10 Restricting access to authenticators on each IT system Zugriffsbeschränkung pro IT-System
Rationale
AC-03 enforces approved access rights on the system's stores of passwords, keys and tokens, for reading and for writing. IA-05 protects authenticator content from unauthorised disclosure and modification, and IA-05(02) enforces authorised access to private keys.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.5.11 Restricting access to authenticators in each application Zugriffsbeschränkung pro Anwendung
Rationale
AC-03 enforces approved access rights on the application's stores of passwords, keys and tokens, for reading and for writing. IA-05 protects the authenticator content the application holds from unauthorised disclosure and modification.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.5.12 Two-person access through split authenticators Zugang nur durch zwei Personen 50%
Rationale
AC-03(02) enforces dual authorisation for defined privileged commands and actions, so two people must act together. That gives the four-eyes principle GS++ applies to data with high confidentiality or integrity needs.
Gaps
GS++ asks for one authenticator to be split between people, such as one holding the token and the other the password. Set up this split knowledge yourself for the actions that need dual authorisation.
Mapped Controls
BER.5.13 Identity check before resetting or replacing authenticators Identität vor Zurücksetzung und Ersetzung
Rationale
IA-05 verifies the recipient's identity when it first distributes an authenticator. It also sets procedures for lost or compromised authenticators, which can include that check. IA-12 validates and verifies identity evidence, which a reset process can use to check the requester.
Gaps
GS++ asks you to check the requester's identity before every reset or replacement. IA-05 states the check for first issue, so write it into your procedure for lost or compromised authenticators.
BER.5.14 Blocking compromised authenticators Kompromittierte Authentifizierungsmittel 85%
Rationale
IA-05 sets administrative procedures for compromised authenticators, such as revoking them. IA-05(01) keeps a list of compromised passwords and rejects any new password found on it.
Gaps
GS++ asks you to block compromised biometric characteristics too, such as fingerprints in unauthorised hands. IA-05(01) keeps a blocklist for passwords, so extend your blocking to biometrics and other authenticators.
Mapped Controls
BER.6.1 Password manager for users Passwortmanager 95%
Rationale
IA-05(18) employs password managers that generate and manage passwords for users. It also protects the passwords the manager stores, which GS++ describes as an encrypted database behind a master password or multi-factor authentication.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.6.2 Blocking password reuse Blockieren von Passwort Recycling 50%
Rationale
IA-05(01)(h) lets the organisation set its own composition rules, which can include a password history. IA-05(08) manages the risk that comes from one person holding accounts on several systems, such as password reuse. IA-05(18) password managers generate a unique password for each account.
Gaps
GS++ asks the system to block a new password that matches an earlier one. SP 800-53 leaves that to the organisation, so add a history rule to your IA-05(01)(h) composition rules.
Mapped Controls
BER.6.3 Blocking trivial passwords Trivialpasswörter 95%
Rationale
IA-05(01) keeps a list of commonly used, expected and compromised passwords. It rejects any new password found on that list, which blocks trivial passwords such as '123456' and passwords exposed in leaks.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.6.4 Criteria for password quality Kriterien für die Qualität von Passwörtern 85%
Rationale
IA-05 asks for authenticators with enough strength of mechanism for their intended use. IA-05(01)(f) allows long passwords and passphrases, and IA-05(01)(h) sets composition and complexity rules.
Gaps
GS++ asks you to base the criteria on a password's lifetime and the ways it can be attacked. Work both into the strength you set for each intended use under IA-05.
Mapped Controls
BER.6.5 Event-driven password changes Anlassbezogene Passwortwechsel 75%
Rationale
IA-05 changes or refreshes authenticators when defined events occur, such as signs of a compromise. An organisation that sets these events and leaves the time period empty gets the event-driven changes GS++ asks for.
Gaps
GS++ asks for password changes only when there is cause, such as a leak or a phishing incident. IA-05 also allows changes on a fixed schedule, so tailor it to events alone.
Mapped Controls
BER.6.6 Monitoring credentials for compromise Monitoring von Zugangsdaten
Rationale
AU-13 monitors open sources for disclosed organisational information, such as leaked credentials, and AU-13(01) uses automated tools to do it. IA-05(01) updates the list of compromised passwords whenever passwords are suspected of exposure.
Gaps
GS++ asks for an automated mechanism that checks your credentials for compromise, for example against leak databases. Include credentials in the information AU-13 monitors for, and automate the check.
BER.7.1 Established algorithms for key generation Etablierte Algorithmen bei der Schlüsselerzeugung
Rationale
SC-12 sets the requirements for key generation. SC-12(02) and (03) produce symmetric and asymmetric keys with approved key management technology and processes. SC-13 implements the type of cryptography each use requires.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
BER.7.2 Key length when generating keys Schlüssellänge
Rationale
SC-12 sets the organisation's key generation requirements, which include key length. SC-13 implements the type and strength of cryptography each use requires, as set by the standards the organisation chooses.
Gaps
GS++ asks for key lengths from a recognised standard, such as BSI TR-02102. Name the standard and its key lengths in your SC-12 key generation requirements.
BER.7.3 Register of public keys Verzeichnis öffentlicher Schlüssel
Rationale
SC-12 manages keys under requirements the organisation defines, which can include a register of public keys and their attributes. SC-17 issues certificates under a certificate policy, and each certificate records the holder's identity, validity, key usage and algorithm.
Gaps
GS++ asks for a register of every public key, with its identity, expiry date, purpose, key type and algorithm. Certificates hold most of these details, so build the register from them and add keys held outside certificates.
BER.7.4 Key generation on secure IT systems Erzeugung auf sicheren IT-Systemen 50%
Rationale
SC-12 sets the requirements for key generation, which can cover the protection of the generating system. SC-12(02) and (03) produce keys with validated or approved key management technology.
Gaps
GS++ asks you to generate each key on a system with at least the protection level of the system that will use it. Add that rule to your SC-12 key generation requirements.
Mapped Controls
BER.7.5 Criteria for random number quality in key generation Kriterien für die Qualität von Zufallszahlen
Rationale
SC-12 sets key generation requirements, which can include criteria for the quality of random numbers. SC-13 implements the required types of cryptography, which can name approved random number generators.
Gaps
GS++ asks you to set criteria for random number generators, such as independently tested generators with an unpredictable source. Write those criteria into your SC-12 key generation requirements.
BER.7.6 Established algorithms for key transport Etablierte Algorithmen beim Transport
Rationale
SC-08(01) uses cryptography to protect the confidentiality and integrity of keys in transit. SC-12 sets the requirements for key distribution. SC-13 implements the type of cryptography each use requires, key transport included.
Gaps
GS++ asks you to transport secret keys with established algorithms only, such as those in BSI TR-02102. Name the algorithms for key transport in your SC-12 and SC-13 settings.
BER.7.7 Transport of private keys only with approval Kein Transport privater Schlüssel
Rationale
IA-05(02) enforces authorised access to the private keys used for public key-based authentication. SC-12 sets requirements for key access and distribution, which can require approval before a private key leaves its system.
Gaps
GS++ asks for a named person or role to approve each export of a private key. Add that approval step to your SC-12 requirements and assign the role.
BER.7.8 Established algorithms for key use Etablierte Algorithmen bei der Schlüsselnutzung 90%
Rationale
SC-13 determines each cryptographic use and implements the type of cryptography it requires. Keys then work only with the approved algorithms set for their use.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
BER.7.9 Purpose binding for keys Zweckbindung
Rationale
SC-12 sets key management requirements, which can bind each key to its registered purpose. SC-17 issues certificates under a certificate policy, and their key usage fields limit what each key may do.
Gaps
GS++ asks you to forbid any use of a key outside its registered purpose, the private key included. Write that rule into your SC-12 requirements and enforce it through key usage settings.
BER.7.10 Stopping encryption and signing with expired keys Abgelaufene Schlüssel 50%
Rationale
SC-12 manages keys over their life cycle under requirements the organisation defines. These can set a cryptoperiod for each key and end its use for encryption or signing once that period is over.
Gaps
GS++ asks you to stop encrypting and signing with a key once its usage period ends. You can still decrypt and verify old data with it. Write this rule into your SC-12 requirements.
Mapped Controls
BER.7.11 Integrity of secret keys Integrität
Rationale
SC-12 sets requirements for storing secret keys and controlling access to them. SI-07 uses integrity verification tools to detect unauthorised changes to defined information, such as stored keys, and SI-07(01) runs the check at defined events.
Gaps
GS++ asks you to verify a secret key's integrity before every use, for example against a checksum held on another system. Add keys to the information SI-07 checks, and make every use a checking event under SI-07(01).
BER.7.12 Authenticity of public keys Authentizität
Rationale
IA-05(02) validates each certificate by building and verifying a certification path to an accepted trust anchor. SC-17 allows only approved trust anchors in the organisation's trust stores.
Gaps
GS++ asks you to check the authenticity of every public key before use, including keys outside certificates, such as SSH host keys. Set up an authenticity check for those keys yourself.
BER.7.13 Validity of keys Gültigkeit
Rationale
IA-05(02) checks certificate status information, revocation included, when it validates a certificate, and keeps a local cache of revocation data. SC-12 manages keys under requirements that include their cryptoperiods.
Gaps
GS++ asks for a validity check before every use of any key, covering its usage period and revocation status. Set that check in your SC-12 requirements for keys used outside authentication.
BER.7.14 Checking keys before they expire Schlüssel vor Ablauf prüfen 50%
Rationale
SC-12 manages keys over their life cycle under requirements the organisation defines. These can include tracking when each key expires and replacing it in good time.
Gaps
GS++ asks you to check keys regularly for an upcoming expiry, so interfaces and applications keep working. Add a schedule for these checks to your SC-12 requirements.
Mapped Controls
BER.7.15 Procedure for retiring secret keys after use Vorgehensweise nach Nutzung 80%
Rationale
SC-12 sets the organisation's requirements for key destruction. These cover secret keys once their task is done, so the organisation takes them out of service in a controlled way.
Gaps
GS++ asks you to delete ephemeral keys straight after the session. Before you retire a key, re-encrypt the data it protects under a new key. Add both steps to your SC-12 procedure.
Mapped Controls
BER.7.16 Rules for key certification Vorgaben für die Schlüsselbeglaubigung
Rationale
SC-12(03) produces asymmetric keys with certificates issued under requirements the organisation defines. SC-17 issues public key certificates under an organisation-defined certificate policy, which sets the rules for certification.
Gaps
GS++ asks you to name a role for certification and to test keys at request, renewal and revocation. Record each key's certification and revocation status in the public key register. Set these rules in your certificate policy, for example one based on RFC 3647.
NOT.1.1 Emergency planning: procedures and rules Verfahren und Regelungen
Rationale
CP-01 sets contingency planning policy and procedures, documents them, gives them to defined roles and names an official to manage them. CP-02 assigns contingency roles and responsibilities with contact details and distributes the plan to key personnel (NOT.1.1.2, NOT.1.1.3).
Gaps
GS++ offers an optional business continuity management system to BSI Standard 200-4 (NOT.1.1.4). It reaches further than contingency planning, so follow that standard if you choose the option.
NOT.1.2 Emergency planning: regular review Regelmäßige Überprüfung
Rationale
CP-01 reviews and updates the contingency planning policy and procedures at a set frequency and after defined events. CP-02 reviews the contingency plan and updates it for changes and for problems found.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.2.1 Emergency and crisis organisation: procedures and rules Verfahren und Regelungen zur BAO
Rationale
CP-02 sets contingency roles and responsibilities, names the people who hold them with contact details and coordinates with incident handling (NOT.2.1.1). CP-04 tests the plan with exercises, such as tabletop exercises, which covers crisis staff exercises (NOT.2.1.4).
Gaps
GS++ asks for a special organisation for emergencies and crises, with a crisis staff and emergency teams, and a way to alert it (NOT.2.1.2). Build it yourself, for example to BSI Standard 200-4, with a crisis staff room if you choose (NOT.2.1.3).
NOT.3.1 Restart plan for time-critical systems and applications Wiederanlaufplan
Rationale
CP-02 sets recovery objectives and restoration priorities, CP-02(03) plans to resume mission and business functions within a set time, and CP-02(08) identifies critical assets. CP-10 recovers and reconstitutes the system to a known state within the recovery objectives.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.3.2 Business continuity plan for time-critical processes Geschäftsfortführungsplan 75%
Rationale
CP-02 identifies essential mission and business functions and plans how to keep them running during a disruption. CP-02(05) plans for the continuance of those functions.
Gaps
CP-02 plans for each system. GS++ asks for a continuity plan for each time-critical business process, including manual workarounds, such as running a digital process on paper. Write these process plans alongside your system plans.
Mapped Controls
NOT.3.3 Awareness of what to do in an emergency Sensibilisierung zum Vorgehen im Notfall 90%
Rationale
CP-03 gives system users contingency training matched to their roles, at set intervals and when systems change. It covers what the organisation expects of each person in an emergency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
NOT.3.4 Functional test of emergency plans Funktionstest 95%
Rationale
CP-04 tests the contingency plan at a set frequency to confirm that it works and that staff are ready. It then reviews the results and corrects the plan. CP-04(04) includes full system recovery in the tests.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
NOT.3.5 Fallback telecommunications services Ausweich-Telekommunikation
Rationale
CP-08 sets up alternate telecommunications services, with agreements that let operations resume when the primary services fail. SC-47 sets up alternate communications paths for command and control, such as out-of-band coordination in a crisis.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.3.6 Security mechanisms for emergencies Sicherheitsmechanismen 90%
Rationale
CP-13 has the organisation use alternative or supplemental security mechanisms when the primary means is unavailable or compromised, as can happen in an emergency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
NOT.4.1 Documentation of backup sources Dokumentation der Quellen 75%
Rationale
CP-09 backs up user-level and system-level information and system documentation on the system components the organisation defines. Those choices set the data each backup covers.
Gaps
GS++ asks for a written list of the data to back up, including data held by service providers or in the cloud. Record your CP-09 choices in that list.
Mapped Controls
NOT.4.2 Backup of IT systems Sicherung des Systems 95%
Rationale
CP-09 backs up system-level information and system documentation at a frequency the organisation sets, in line with its recovery time and recovery point objectives.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
NOT.4.3 Backup of applications Sicherung der Anwendung 90%
Rationale
CP-09 backs up user-level and system-level information, such as application data and configuration, at a set frequency. It applies to the system components the organisation defines, applications among them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
NOT.4.4 Automated backup Automatische Datensicherung 50%
Rationale
CP-09 runs backups of user-level and system-level information at a frequency set to meet the recovery time and recovery point objectives.
Gaps
GS++ asks for backups to run through an automated mechanism, such as backup software or scheduled scripts, which avoids human error and omissions. Automate your CP-09 backups to meet the requirement.
Mapped Controls
NOT.4.5 Archiving data needed in the long term Archivierung langfristig benötigter Daten 50%
Rationale
SI-12 manages and retains information as laws, regulations, policy and operational needs require. That covers long-term archiving of the information the organisation must retain.
Gaps
GS++ asks for archived data to stay usable over time. Archive with it the assets needed to use the data, such as software and keys (NOT.4.5.1), and the documentation (NOT.4.5.2).
Mapped Controls
NOT.4.6 Protected storage of backups Geschützte Aufbewahrung
Rationale
CP-09 protects the confidentiality, integrity and availability of backup information, and CP-09(03) stores backup copies in a separate facility or fire-rated container. MP-04 physically controls backup media and stores them securely within controlled areas.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.4.7 Versioned backups Versionierte Datensicherung 50%
Rationale
CP-09 runs backups at a frequency set by the recovery point objective. Its frequency and retention settings can provide several generations of backups.
Gaps
GS++ asks for backup versions from different points in time, so data deleted before the last backup can be restored. Set retention to hold several generations, such as three each for the last hours, days, weeks and months.
Mapped Controls
NOT.4.8 Encrypted backups Verschlüsselte Datensicherung
Rationale
CP-09(08) uses cryptographic mechanisms to prevent unauthorised disclosure and modification of backup information. SC-13 implements the required type of cryptography for each use, in line with recognised standards.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.4.9 Dedicated storage media for backups Speichermedien 45%
Rationale
CP-09(01) tests backup information to verify the reliability of the storage media and the integrity of the information on them.
Gaps
GS++ asks for storage media used only for backups and suited to the set retention period, which can run from months to years. Choose media that stay readable for that long.
Mapped Controls
NOT.4.10 Separate storage of backups Getrennte Aufbewahrung
Rationale
CP-06 sets up an alternate storage site for backups, and CP-06(01) separates it from the primary site. CP-09(03) stores backup copies in a separate facility or fire-rated container away from the operational system.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.4.11 Media archive Datenträgerarchiv
Rationale
MP-04 physically controls media and stores them securely in controlled areas, such as a locked media archive. CP-09(03) stores backup copies in a separate facility or fire-rated container.
Gaps
GS++ asks for a dedicated locked room for long-term media storage, in a different fire compartment from the original data. Choose such a room as your controlled area.
NOT.4.12 Geo-redundant storage of backups Georedundanz
Rationale
CP-06(01) places the alternate storage site far enough from the primary site that the same threats are unlikely to hit both. CP-09(05) transfers backup information to that alternate storage site.
Gaps
GS++ usually takes geo-redundant to mean 200 km or more in a straight line from the original data. Use that figure when you choose the alternate storage site.
NOT.4.13 Data sovereignty for data held by service providers Datensouveränität
Rationale
CP-09 backs up information on the system components the organisation defines, which can include those at service providers. SA-09 requires external service providers to meet the organisation's requirements, such as regular data exports in portable formats.
Gaps
GS++ asks for regular backups of provider-held data in an open standard format, such as JSON or CSV, under your own control. Make these part of your exit strategy for each provider.
NOT.4.14 Offline copy of backups Offline-Kopie
Rationale
CP-09 runs backups at a set frequency, and CP-09(03) holds copies apart from the operational system. SC-28(02) moves defined information from online storage to secure offline storage.
Gaps
GS++ asks for an offline copy of the backups on a fixed schedule, separated physically or logically from production systems and the network. Set the interval, such as daily or weekly, by how critical the data is.
NOT.4.15 Restore procedure Vorgehen zur Wiederherstellung
Rationale
CP-02 sets restoration priorities and plans full system restoration while preserving the controls in place. CP-10 provides for recovery and reconstitution of the system to a known state.
Gaps
GS++ asks for a written, step-by-step restore procedure, covering for example the order for restoring critical systems and where each backup is stored. Maintain it as a separate document, ready for an emergency.
NOT.4.16 Testing backups Test der Datensicherung
Rationale
CP-09(01) tests backup information for media reliability and integrity, and CP-09(02) restores a sample of backups during plan testing (NOT.4.16.1). CP-04 tests the contingency plan, including recovery, at a set frequency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
NOT.4.17 Testing applications after a restore Anwendungstest
Rationale
CP-04(04) includes full recovery and reconstitution of the system to a known state in contingency plan testing. CP-09(02) restores selected system functions from sampled backups.
Gaps
GS++ asks you to check that each restored application works, including its data integrity and configuration. Add those functional checks to your recovery tests.
DET.1.1 Detection: procedures and rules Verfahren und Regelungen
Rationale
IR-01 sets incident response policy and procedures that cover detection and analysis. It documents them, sets roles and responsibilities and gives them to the people in those roles. SI-01 does the same for system monitoring, and AU-01 for logging.
Gaps
GS++ asks for procedures and rules for detecting security incidents. SP 800-53 spreads detection across its incident response, system integrity and logging policies. Check that together they describe how you detect incidents.
DET.1.2 Detection: regular review Regelmäßige Überprüfung
Rationale
IR-01 reviews and updates the incident response policy and procedures at a set frequency and after events you define, such as a serious incident. AU-01 does the same for logging, and SI-01 for system monitoring.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.2.1 Reporting procedure for security events Meldeverfahren
Rationale
IR-06 has staff report suspected incidents to the incident response capability within a set time. IR-07 gives users a support resource that advises them on handling and reporting incidents, including immediate actions they take themselves (DET.2.1.1). IR-08 sets out in the incident response plan which incidents to report and how to share incident information.
Gaps
GS++ also asks for report forms and a procedure for feedback to the people who report. Add both to your reporting procedure.
DET.2.2 Security operations center Security Operations Center
Rationale
IR-04(14) sets up and maintains a security operations center, whose staff detect, analyse and respond to incidents. IR-08 names in the incident response plan the people or roles responsible for incident response.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.2.3 Round-the-clock on-call duty Ständiger Bereitschaftsdienst 50%
Rationale
IR-04 sets up an incident handling capability. IR-04(14) adds a security operations center that monitors for incidents on an ongoing basis and responds to them.
Gaps
GS++ asks for someone on call around the clock who starts work on a security alert straight away. Set up that rota yourself, and decide which alerts call them out, based on how critical the affected systems are.
Mapped Controls
DET.3.1 Logging of security-relevant events Protokollierung sicherheitsrelevanter Ereignisse
Rationale
AU-02 sets the event types to log, such as authentications, commands, device connections and errors, and AU-12 generates records for them. AU-03 records what happened, when, where, the source, the outcome and who was involved (DET.3.1.7). AC-06(09) logs the use of privileged functions (DET.3.1.8). AU-11 keeps the records for a set period.
Gaps
GS++ names specific events to log, such as executed commands and connected peripherals. AU-02 leaves the list of events to you, so add the ones GS++ names.
DET.3.2 Integration of cloud services into the audit log Integration von Cloud-Diensten
Rationale
AU-12(01) compiles audit records from defined components, which can include cloud services, into one system-wide audit trail. AU-16 coordinates audit information with external organisations, such as cloud providers, and AU-16(02) shares it under agreements.
Gaps
GS++ asks you to record events from your cloud services in your own audit log. Name each cloud service as a source for the audit trail, and agree with the provider how its logs reach you.
DET.3.3 Filtering of unneeded log content Filterung nicht benötigter Inhalte
Rationale
AU-02 selects the event types worth logging and records why, which keeps unneeded events out of the log. AU-03(03) limits personal data in audit records to the elements you define as needed.
Gaps
GS++ also covers content beyond personal data, such as business secrets. Set your own criteria for removing or masking it, especially before logs go to another organisation or a cloud provider.
DET.3.4 Log storage capacity Speicherkapazität
DET.3.5 Audit-proof logging Revisionssicherheit 85%
Rationale
AU-09 protects audit information from unauthorised changes and deletion and raises an alert when someone tampers with it. AU-09(02) stores audit records on a separate system, AU-09(03) checks their integrity with cryptography and AU-09(04) limits who can manage logging.
Gaps
GS++ asks you to document every authorised change to the audit log in an audit-proof way. Keep that record yourself, for example with cryptographic hashes or version control stored apart from the log.
Mapped Controls
DET.3.6 Non-repudiation Unbestreitbarkeit 90%
Rationale
AU-10 provides irrefutable evidence that an individual performed the actions you define, such as a high-value transfer. AU-10(01) binds the identity of whoever produced a piece of information to that information.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
DET.4.1 Monitoring of logging Überwachung der Protokollierung
Rationale
AU-05 alerts defined roles when audit logging fails, and AU-05(02) does so in real time. SI-06 checks that security functions, such as logging, work correctly and alerts on failure.
Gaps
GS++ also asks you to watch how much log data arrives from each source over time. Set an expected volume per source and raise an alert when it drops.
DET.4.2 Automated attack detection Automatische Angriffserkennung
Rationale
SI-04 monitors systems for attacks and signs of attack. SI-04(02) analyses events with automated tools in near real time, and SI-04(23) adds host-based monitoring. SI-03 detects malicious code with signature-based and behaviour-based mechanisms.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.4.3 Monitoring of attack detection Überwachung der Angriffserkennung
Rationale
SI-04(09) tests the intrusion monitoring tools at a set frequency. SI-06 checks that security functions, such as attack detection, work correctly and alerts on failure.
Gaps
GS++ asks for a continuous watch on attack detection, with an alert as soon as anyone switches it off or its services stop. Set up that alert alongside the periodic tests.
DET.4.4 Changes to automated security policies Änderungen an Sicherheitsrichtlinien
Rationale
AC-02(07) monitors privileged role assignments and role changes, such as new members of admin groups. CM-03 monitors configuration-controlled changes, and CM-03(07) reviews them to catch unauthorised ones. CM-06 monitors and controls changes to configuration settings, such as firewall rules and antivirus exclusions.
Gaps
GS++ also asks you to watch for security policies and tools being switched on or off. Add those events to the changes you monitor.
DET.4.5 Unwanted data leakage Unerwünschte Datenabflüsse
Rationale
SI-04(04) monitors outbound traffic for unusual or unauthorised activity, and SI-04(18) analyses it for covert exfiltration. SC-07(10) prevents exfiltration at the boundary and tests for it. SI-20 embeds tainted data that shows whether information has left the organisation.
Gaps
GS++ also covers data leaving through endpoints, such as copies to removable media. Add data loss prevention on endpoints to the network monitoring.
DET.4.6 Anomalous application use Anomale Nutzung der Anwendung
Rationale
SI-04 identifies unauthorised use, and SI-04(13) builds profiles of normal activity so that anomalies stand out. AU-06 reviews audit records for inappropriate or unusual activity. AC-02(12) monitors accounts for atypical use and reports it (DET.4.6.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.4.7 Expiry of domain names Auslaufen von Domains 0%
Rationale
SP 800-53 leaves watching domain registrations to the organisation.
Gaps
No SP 800-53 control is mapped to this requirement. GS++ suggests watching for the expiry of the organisation's domain registrations. Keep an inventory of your domains with their expiry dates, and set reminders well before each one runs out.
DET.4.8 Issue of new HTTPS certificates Ausstellung neuer HTTPS-Zertifikate 35%
Rationale
SC-17 issues and manages public key certificates, such as the X.509 certificates behind HTTPS, under a certificate policy. That policy can cover renewing each certificate in good time.
Gaps
GS++ asks you to monitor that each internet-facing server gets a new certificate before the old one expires. Add expiry and renewal monitoring yourself, for example with an alert well before the expiry date.
Mapped Controls
DET.4.9 Check-up for tampering Manipulations-Checkup
Rationale
SR-10 inspects systems or components at random, at a set frequency or on indication, to detect tampering. SR-09 runs a tamper protection programme for the system and its components. PE-03(05) uses anti-tamper technologies, such as seals, to detect physical tampering.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.4.10 Host-based decoys Host-basierte Köder
Rationale
SC-26 places decoy components in systems to attract attacks, so the organisation can detect and analyse them. SI-20 embeds data, such as canary files or honeytokens, to detect misuse or removal of information.
Gaps
GS++ asks for decoys on the hosts themselves, such as fake files or credentials that raise an alert when touched. Plan which lures go on which hosts, and who gets the alert.
DET.4.11 Anomalies in networks and at the perimeter Anomalien in Netzen und am Perimeter
Rationale
SC-07 monitors communications at external and key internal interfaces. SI-04 detects unauthorised network connections, and SI-04(04), (11) and (13) watch traffic for anomalies against profiles of normal activity. AC-17(01) monitors remote access, including authentication attempts at external interfaces (DET.4.11.1). SC-26 deploys decoys, such as network honeypots (DET.4.11.2).
Gaps
GS++ asks you to watch critical traffic flows against criteria you set (DET.4.11.3). Define those flows and criteria yourself, for example connections to unknown domains or large uploads to cloud storage.
DET.4.12 Monitoring of network availability Monitoring der Netzverfügbarkeit
Rationale
CA-07 monitors system metrics you define, such as network availability against thresholds. SC-05(03) monitors for signs of denial of service and checks that resources, such as bandwidth, suffice (DET.4.12.1). SC-05(02) manages capacity and bandwidth.
Gaps
GS++ asks for routine monitoring of network availability and load, against thresholds. SC-05 looks at denial of service, so add both as CA-07 metrics with your own thresholds.
DET.4.13 Availability of the host system Verfügbarkeit des Hostsystems
Rationale
CA-07 monitors system metrics you define, such as whether a host can be reached, against thresholds. SC-05(03) monitors for signs of a denial-of-service attack against the host and its resources.
Gaps
GS++ asks for routine reachability monitoring of each host, against thresholds. SC-05 looks at denial of service, so add reachability as a CA-07 metric, with thresholds such as failed checks in a set time.
DET.4.14 Availability of the application Verfügbarkeit der Anwendung
Rationale
CA-07 monitors system metrics you define, such as whether an application can be reached, against thresholds. SC-05(03) monitors for signs of a denial-of-service attack that affects the application.
Gaps
GS++ asks for routine reachability monitoring of the application's own service, against thresholds. SC-05 looks at denial of service, so add service reachability as a CA-07 metric with your own thresholds.
DET.4.15 Resource utilisation of host systems Ressourcenauslastung von Hostsystemen 55%
Rationale
SC-05(03) monitors the system resources you define on a host, such as CPU, memory and storage. It checks that enough capacity remains to withstand a denial-of-service attack.
Gaps
GS++ asks for routine monitoring of host resources against thresholds. SC-05 looks at denial of service, so set your own thresholds from a baseline of normal use.
Mapped Controls
DET.4.16 Resource utilisation of server services Ressourcenauslastung der Server-Dienste 50%
Rationale
SC-05(03) monitors the resources you define, such as those of the server services an application uses. It checks that enough capacity remains to withstand a denial-of-service attack.
Gaps
GS++ asks for routine monitoring of the load on an application's server services, such as the number of connected clients. SC-05 looks at denial of service, so set your own thresholds from a baseline of normal use.
Mapped Controls
DET.4.17 Application-based capacity management Anwendungsbasiertes Kapazitätsmanagement
Rationale
CA-07 monitors metrics you define over time, such as an application's load across its systems. SC-05(03) monitors defined system resources to check that enough remain.
Gaps
GS++ asks you to manage capacity for the application as a whole, across its systems and over time, with peaks and averages. Build that view yourself from the CA-07 metrics.
DET.4.18 Public email blocklists Öffentliche Blocklisten 0%
Rationale
SP 800-53 leaves checking public blocklists to the organisation.
Gaps
No SP 800-53 control is mapped to this requirement. GS++ suggests checking public blocklists regularly for entries that name the organisation's own mail servers.
DET.4.19 Unauthorised transmitters Unautorisierte Sendeanlagen
Rationale
RA-06 runs technical surveillance countermeasures surveys at defined locations to find hidden transmitters, such as bugs. SI-04(14) uses a wireless intrusion detection system to find rogue wireless devices.
Gaps
GS++ asks for automated monitoring of rooms for every kind of transmitter. SI-04(14) covers rogue wireless network devices, and RA-06 surveys run at intervals. Add automated detection for other transmitters, such as hidden bugs, where a room needs it.
DET.5.1 Timely vulnerability management Zeitnahes Schwachstellenmanagement
Rationale
RA-05 monitors and scans for vulnerabilities, analyses the results and remediates them within response times set by risk (DET.5.1.1). SI-02 identifies, reports and corrects flaws, and SI-02(03) sets benchmarks for the time to fix them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.5.2 Vulnerability register Schwachstellenregister
Rationale
CA-05 records known vulnerabilities and their planned remediation in a plan of action and milestones, and keeps it up to date. RA-05 analyses scan reports and shares the findings with defined roles.
Gaps
GS++ asks you to record each vulnerability when you find it, with the affected components, its criticality and its status. Keep that register yourself, for example in a vulnerability management tool that updates automatically.
DET.5.3 Vulnerability scans Schwachstellenscans 90%
Rationale
RA-05 scans for vulnerabilities, analyses the results and remediates them. RA-05(05) authorises privileged access for scanning (DET.5.3.1). RA-05(06) and (10) compare and correlate scan results (DET.5.3.2). RA-05(08) reviews historic audit logs to find out whether a vulnerability was exploited earlier (DET.5.3.3).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
DET.5.4 Regular penetration tests Regelmäßige Penetrationstests 90%
Rationale
CA-08 runs penetration tests on defined systems at a set frequency. The testers use the methods of real attackers, which shows how well the systems actually defend themselves.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
DET.5.5 Red teaming Red Teaming 95%
Rationale
CA-08(02) runs red team exercises, in which testers attempt a realistic attack on the organisation's systems. CA-08(01) has an independent agent or team carry out the tests.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
DET.5.6 Threat hunting Threat Hunting 95%
Rationale
RA-10 sets up and maintains a threat hunting capability. It searches the organisation's systems for indicators of compromise at a set frequency, looking for attacks already under way.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
DET.5.7 Covert channel analysis Analyse verdeckter Kanäle
Rationale
SC-31 analyses the system for covert storage and timing channels and estimates their bandwidth. SI-04(18) analyses outbound traffic to detect information leaving through covert channels.
Gaps
GS++ also asks for a check for covert channels whenever an incident involves one. Add that check to your incident handling.
DET.5.8 Threat analysis Bedrohungsanalyse
Rationale
RA-03(03) keeps track of the current cyber threat environment on an ongoing basis. SI-05 receives security alerts and advisories from outside and passes them on. PM-16 runs a threat awareness programme that shares threat intelligence with other organisations. RA-05(04) finds what information about the system is publicly discoverable (DET.5.8.1). AU-13 monitors open sources for unauthorised disclosure of the organisation's information, and AU-13(01) automates it (DET.5.8.1.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.5.9 External vulnerability reports Externe Schwachstellenmeldungen
Rationale
RA-05(11) sets up a public channel for receiving vulnerability reports from outside the organisation. SI-02 corrects the reported flaws and installs the fixes within a set time.
Gaps
GS++ adds an optional bonus programme for people who report vulnerabilities, such as a bug bounty (DET.5.9.1). Set up the rewards and rules yourself if you take it on.
DET.5.10 Timely patch management Zeitnahes Patchmanagement
Rationale
SI-02 tests security updates and installs them within a set time, and SI-02(02) and (04) automate patch status checks and patching (DET.5.10.2, DET.5.10.3). CM-14 installs components only with a verified signature from an approved certificate, which limits patches to trusted sources (DET.5.10.1). SI-07(15) authenticates software and firmware before installation (DET.5.10.4). CM-03 runs patches through configuration change control (DET.5.10.5).
Gaps
GS++ asks you to approve reliable sources for patches (DET.5.10.1). CM-14 covers that for signed patches, so also approve the sources for patches that come unsigned.
DET.6.1 Assessment of security events Beurteilung von Ereignissen
Rationale
AU-06 reviews and analyses audit records for unusual activity and reports what it finds, and AU-06(01) automates the process. IR-04 makes detection and analysis part of incident handling. IR-05 tracks and documents incidents, and IR-05(01) collects and analyses incident information automatically (DET.6.1.1, DET.6.1.3). SI-04(05) and (12) alert defined roles automatically on signs of compromise (DET.6.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DET.6.2 Assessment of incoming files Beurteilung von Eingängen
Rationale
SI-03 scans files from external sources at entry points and blocks or quarantines malicious code. SC-44 runs suspicious files in a detonation chamber, an isolated environment, to examine what they do (DET.6.2.1).
Gaps
GS++ also asks for a scanning station for removable media (DET.6.2.2). It has staff release files the scanner is unable to check, such as password-protected ones, before users get them.
REA.1.1 Incident handling: procedures and rules Verfahren und Regelungen
Rationale
IR-01 sets incident response policy and procedures, documents them, gives them to the roles that need them and names an official to manage them. IR-08 sets out an incident response plan that assigns responsibilities and goes to the responders. IR-04 puts the procedures into practice through an incident handling capability.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
REA.1.2 Incident handling: regular review Regelmäßige Überprüfung
Rationale
IR-01 has the organisation review and update its incident response policy and procedures at a set frequency and after defined events. IR-08 reviews the incident response plan at a set frequency and updates it after changes or when problems come to light.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
REA.1.3 Incident handling exercises Übungen zur Vorfallsbehandlung
Rationale
IR-03 tests the incident response capability at a set frequency, for example through exercises and simulations. IR-02(01) builds simulated events into incident response training, so responders practise realistic situations.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
REA.2.1 Triage and first response Triage und Erstreaktion 65%
Rationale
IR-04 handles incidents from detection and analysis onward, and the analysis step includes a first assessment of each report. IR-04(03) defines incident classes, each with a set first response.
Gaps
GS++ asks you to give every incident report a priority, so critical incidents get attention first. Add a priority scale to the first assessment.
Mapped Controls
REA.2.2 Automatic first response Automatische Erstreaktion
Rationale
IR-04(01) automates incident handling and IR-04(02) reconfigures systems dynamically. IR-04(05) disables a system automatically when it detects defined security violations. SI-04(07) alerts responders and takes the least disruptive action automatically to stop suspicious events, as intrusion prevention systems do.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
REA.2.3 Documenting incidents Dokumentation von Vorfällen 90%
Rationale
IR-05 tracks and documents each security incident. The records support later analysis of incident details and of trends across incidents.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
REA.2.4 Diagnostic data for incidents Diagnosedaten
Rationale
AU-12(03) lets authorised staff change what is logged, within set time limits, when an incident needs more detail. IR-04(12) analyses malicious code and other artefacts left behind, and IR-04(13) analyses unusual behaviour. SI-04 deploys monitoring at ad hoc locations and raises the level of monitoring when the risk changes.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
REA.2.5 IT forensics IT-Forensik
Rationale
IR-04(12) analyses malicious code and other artefacts left after an incident. AU-09 protects audit information from unauthorised access and change, and AU-09(03) adds cryptographic integrity, which keeps evidence sound. IR-05 keeps incident records with the information forensics needs. IR-07 gives access to forensic services, and IR-07(02) sets up relations with external providers.
Gaps
GS++ asks for legally sound documentation of evidence. It also suggests a two-person rule for forensic work and a forensic service provider on call within an agreed time. Agree that response time in the contract with the provider.
REA.2.6 Root cause analysis and remediation Ursachenanalyse und Behandlung
Rationale
SI-02(07) analyses the root cause of a flaw and acts on it. IR-04 handles each incident from containment to recovery and coordinates the response inside and outside the organisation (REA.2.6.3). IR-04(15) handles public relations. IR-05 documents each incident and the handling steps (REA.2.6.1). IR-06 reports incident information to the relevant authorities (REA.2.6.2.1). IR-08 assigns responsibilities and plans how incident information is shared, and IR-08(01) covers notifying those affected by a breach.
Gaps
GS++ asks for an escalation ladder and suggests service levels for how fast incidents are handled (REA.2.6.5, REA.2.6.4). Set both out in the incident response plan.
REA.3.1 Improvement through lessons learned Verbesserung durch Erkenntnisse
Rationale
IR-04 builds lessons learned from incidents into incident response procedures and training, and puts the changes in place. AT-02 adds lessons from incidents to awareness training. IR-05 keeps incident records, and IR-05(01) collects and analyses them, including the type and extent of each incident (REA.3.1.1).
Gaps
GS++ asks for a regular review of all existing security measures in the light of incident findings. It also asks you to record the damage each incident caused, along with its type and extent.
KONF.1.1 Configuration: procedures and rules Verfahren und Regelungen
Rationale
CM-01 sets the configuration management policy and procedures, documents them and gives them to the roles that need them (KONF.1.1.1, KONF.1.1.3). CM-09 adds a configuration management plan that sets roles, responsibilities and processes, which assigns the tasks to people or roles (KONF.1.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.1.2 Configuration: regular review Regelmäßige Überprüfung 95%
Rationale
CM-01 has the organisation review and update its configuration management policy and procedures at a set frequency. It also calls for a review after events the organisation defines, which can include the triggers GS++ gives, such as a serious security incident.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.1.3 Management of configuration tools Management von Werkzeugen
Rationale
CM-08 keeps an inventory of system components, which can list each configuration tool with details the organisation chooses, such as its purpose and supplier. SR-04 documents and maintains the provenance of each tool, which records where it comes from.
Gaps
GS++ asks for a record of the configuration tools in use, with each tool's purpose and origin. Add the tools to the inventory with purpose and source as fields, and cover them in your provenance records.
KONF.1.4 Restricting access to configuration documentation Einschränkung des Zugriffs auf Dokumentation
Rationale
AC-03 enforces approved authorisations for access to stored configuration documents and the repositories that hold them. AC-06 limits that access to the people and processes that need it. AC-06(01) does the same for security-relevant information, such as configuration parameters. MP-02 restricts access to digital and paper media that hold configuration documents.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.1.5 Encryption of configuration secrets Verschlüsselung von Konfigurationsgeheimnissen
Rationale
IA-05 protects authenticator content, and IA-05(07) keeps unencrypted static credentials out of applications and storage. SC-28(01) encrypts sensitive information at rest, such as secrets in configuration files and vaults. SC-12 manages the keys that protect the secrets, including the key that unlocks a secret store.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.2.1 Baseline configuration for systems Grundkonfiguration für Systeme
Rationale
CM-02 develops, documents and maintains a baseline configuration under configuration control. CM-02(03) keeps previous versions for rollback (KONF.2.1.1). CM-06 establishes and documents the security configuration settings that make up the baseline, based on common secure configurations such as benchmarks.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.2.2 Cryptographic methods in IT systems Kryptographische Verfahren in IT-Systemen
Rationale
SC-13 determines the cryptographic uses on each system and implements the type of cryptography each use needs. SC-12 establishes and manages the keys that the activated cryptographic functions depend on.
Gaps
GS++ asks for cryptography to recognised standards, such as BSI TR-02102. It also asks for the settings to follow its access rights practice (BER). Name those standards when you set SC-13's parameters.
KONF.2.3 Default credentials in IT systems Default-Zugangsdaten in IT-Systemen 95%
Rationale
IA-05 has the organisation change default authenticators before first use. That covers factory-set credentials, such as the user names 'root' or 'administrator' with published passwords, which an attacker can find with little effort.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.2.4 Disabling unneeded system functions Deaktivierung nicht benötigter Systemfunktionen
Rationale
CM-07 limits each system to essential capabilities and disables unneeded functions, ports, protocols and services, including cloud connections (KONF.2.4.2). CM-06 applies the most restrictive settings that operations allow, such as turning off weak protocols and telemetry. SC-17 keeps only approved trust anchors in certificate stores, which removes unneeded certificates (KONF.2.4.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.2.5 Review of the system configuration Überprüfung der Systemkonfiguration
Rationale
CM-06 monitors and controls changes to configuration settings, and CM-06(01) verifies the settings with automated mechanisms (KONF.2.5.1). CM-03(07) reviews system changes at a set frequency to find unauthorised ones.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.2.6 Mobile device management Mobile Device Management
Rationale
AC-19 sets configuration and connection requirements for organisation-controlled mobile devices and authorises their connection. CM-06(01) manages, applies and verifies device settings centrally with automated mechanisms, which is the job of a mobile device management (MDM) system.
Gaps
GS++ asks for an MDM to manage mobile devices. BSI's minimum standard for MDM adds features, such as detecting jailbroken or rooted devices, so use it to choose and set up the product.
KONF.2.7 Sovereign tools Souveräne Werkzeuge
Rationale
SA-09(05) restricts where external services process and store data, which keeps control over jurisdiction and lets tools run in the organisation's own infrastructure. SR-03 applies supply chain controls that limit harm from supplier events, such as a withdrawn service or changed licence. SR-05 uses acquisition strategies that reduce dependence on external suppliers, such as choosing tools that run locally.
Gaps
GS++ asks for tools the organisation can run independently of vendors, cloud providers and state influence. Make that independence a criterion when you choose and buy tools.
KONF.2.8 Alternative administrative access Alternative Administrationszugänge
Rationale
AC-02 defines emergency account types, such as break-glass administrator accounts, and the conditions for their use. CP-11 provides alternative communications protocols to keep operating when the primary one fails. SC-47 sets up alternate communications paths for system operations, such as out-of-band management.
Gaps
GS++ asks for a second way to administer central systems, such as console, command-line or API access, for when the usual management interface fails. Set up and document these alternative tools and interfaces.
KONF.2.9 Secure and authenticated boot process Abgesicherter und authentisierter Bootprozess 85%
Rationale
SI-07(09) verifies the integrity of the boot process, and SI-07(10) protects boot firmware. SI-07(06) adds cryptographic mechanisms that detect unauthorised changes to software and firmware.
Gaps
GS++ asks for hardware trust anchors and a multi-stage boot that checks each step cryptographically, such as Secure Boot on UEFI or ARM systems. Choose hardware and firmware that support this.
Mapped Controls
KONF.3.1 Cryptographic hardware storage Kryptographischer Hardwarespeicher
Rationale
SC-28(03) provides protected storage for cryptographic keys, such as a hardware-protected key store or Trusted Platform Module (TPM). SC-12 sets the key management requirements for storing keys and controlling access to them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.3.2 Storage encryption Speicherverschlüsselung
Rationale
SC-28(01) encrypts information at rest on system components, including built-in storage. AC-19(05) asks for full-device or container encryption on mobile devices. SC-13 implements the approved type of cryptography for that encryption.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.3.3 SIM PIN SIM-PIN
Rationale
AC-19 sets configuration requirements for mobile devices, which can include an active SIM PIN. IA-07 authenticates the user to a cryptographic module. A SIM card is such a module, and the SIM PIN is that authentication.
Gaps
GS++ asks for a SIM PIN on every system with a cellular connection, to protect the subscription if the SIM card is lost or stolen. Make the SIM PIN part of the configuration for each such system.
KONF.3.4 Physical theft protection Physischer Diebstahlschutz
Rationale
PE-03(04) uses lockable physical casings to protect system components from unauthorised physical access. AC-19 sets requirements for mobile devices, including their protection outside controlled areas, where the risk of theft arises.
Gaps
GS++ asks for physical theft protection, such as cable locks that fix a laptop to a desk or other fixed object. Add such locks to your protection measures for mobile devices.
KONF.3.5 Remote location detection Standortbestimmung
Rationale
CM-08(08) uses automated mechanisms to track system components by geographic location. PE-20 uses asset location technologies to track and monitor where assets are and how they move.
Gaps
GS++ asks for a way to find a system's location remotely, wherever it is. PE-20 tracks assets within controlled areas, so use CM-08(08) for devices outside them.
KONF.3.6 Remote wipe or lock Fernlöschung oder -sperre
Rationale
MP-06(08) provides the means to purge or wipe information remotely, or under set conditions such as long inactivity (KONF.3.6.1). AC-19 sets configuration requirements for mobile devices, which can include remote locking through device management.
Gaps
GS++ asks for a remote lock as well as a remote wipe. A lock makes the device unusable and leaves its data in place, so add remote lock to your mobile device requirements.
KONF.3.7 Restricting connected peripherals Einschränkung angeschlossener Peripherie
Rationale
CM-07(09) prohibits the use or connection of unauthorised hardware. SC-41 disables unneeded connection ports and input and output devices, such as USB and Bluetooth, physically or logically. MP-07 restricts the use of removable media types, such as USB sticks.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.3.8 Restricting removable media Einschränkung von Wechselmedien
Rationale
CM-07 restricts unneeded functions such as automatic mounting, and CM-07(02) can block auto-execute features. MP-07 restricts the use of removable media on systems. SC-18(04) prevents automatic execution of mobile code, which includes turning off auto-execute for CDs, DVDs and USB devices.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.4.1 Connection to a directory service Anbindung an Verzeichnisdienst
Rationale
IA-13 uses identity providers and authorisation servers to manage identities and access rights centrally. AC-02(01) manages system accounts with automated mechanisms. IA-02 authenticates users against the directory, with single sign-on under IA-02(10). IA-05 protects authenticators, which is the basis for turning off the forwarding of reusable credentials (KONF.4.1.1).
Gaps
GS++ asks for systems to stop forwarding reusable credentials, for example through SSH agent forwarding or credential delegation. Turn those features off in each system's configuration.
KONF.4.2 Connection to DNS servers DNS-Anbindung
Rationale
CM-06 sets the DNS resolvers the organisation authorises as a fixed configuration setting. SC-08(01) encrypts DNS traffic in transit, for example with DNS over TLS or HTTPS (KONF.4.2.1). SC-21 has clients validate DNS responses or use authenticated channels to trusted resolvers.
Gaps
GS++ asks for each system to use only the DNS resolvers the organisation has authorised. SC-21 focuses on validating responses, so keep a list of approved resolvers and enforce it through CM-06.
KONF.4.3 Authentication of remote maintenance functions Authentifizierung von Fernwartungsfunktionen
Rationale
MA-04 asks for strong authentication when nonlocal maintenance and diagnostic sessions start. IA-02 uniquely identifies and authenticates the administrators who use remote maintenance, and IA-02(01) adds multi-factor authentication for privileged accounts. AC-17 authorises each type of remote access before connections are allowed.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.4.4 Restricting remote maintenance functions Einschränkung von Fernwartungsfunktionen
Rationale
AC-17 sets usage restrictions and configuration requirements for each type of remote access, and AC-17(04) limits privileged commands over remote access. CM-07 turns off unneeded remote session features, such as clipboard, drive and device redirection. MA-04 allows nonlocal maintenance tools only as policy and the security plan permit.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.4.5 Time sources Zeitquellen 85%
Rationale
SC-45 synchronises system clocks, which keeps log timestamps consistent across systems. SC-45(01) compares and synchronises the clocks with an authoritative time source the organisation defines, and SC-45(02) adds a secondary source.
Gaps
GS++ asks for authorised time sources. Authenticate each source to confirm it is the one you authorised, for example with Network Time Security (NTS) or authenticated NTP.
Mapped Controls
KONF.5.1 Authentication to the system Authentifizierung am System
Rationale
IA-02 uniquely identifies and authenticates users before they access the system, including before boot (KONF.5.1.2). AC-11 keeps a locked device locked until the user authenticates again. CM-05 restricts who can change firmware settings, for example with a UEFI administrator password (KONF.5.1.1).
Gaps
GS++ asks for authentication to the firmware and, on mobile devices, before the operating system starts. Scope IA-02 and CM-05 to cover both, for example with a firmware password and pre-boot authentication.
KONF.5.2 One account signed in at a time Keine Mehrfachanmeldung 55%
Rationale
AC-10 limits the number of concurrent sessions for each account or account type. A system-wide limit of one session stops several accounts from being signed in at once.
Gaps
GS++ asks each system to allow one signed-in account at a time. AC-10's discussion sets aside one user working through several accounts, so configure the system to refuse a second sign-in.
Mapped Controls
KONF.6.1 Minimum required access rights for applications Minimal erforderliche Berechtigungen für Anwendungen
Rationale
AC-06 grants applications and processes only the access rights their tasks need. AC-03(12) has applications declare the access they need and blocks the rest. SC-39 runs each process in its own execution domain, and CM-07(06) runs chosen software in a confined environment (KONF.6.1.2). AC-19(05) uses container-based encryption on mobile devices, which encapsulates the data (KONF.6.1.1). SC-50 separates security domains in software, such as work and personal profiles (KONF.6.1.3).
Gaps
GS++ asks for data encapsulation (KONF.6.1.1). SP 800-53 reaches it through container encryption and process isolation, so check that these keep each application's data apart.
KONF.6.2 Shared directories Gemeinsam genutzte Verzeichnisse
Rationale
AC-03 enforces access rights on shared directories, for example with the sticky bit, which lets only a file's owner delete or rename it. AC-06 gives each user and process only the access to shared directories that their tasks need.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.3 Kiosk mode Kiosk-Modus 85%
Rationale
SI-14 runs components non-persistently. They start in a known state and reset at the end of each session, and SI-14(01) refreshes them from trusted sources. That clears changes left behind by malware or earlier users.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.6.4 Privileged system functions Privilegierte Systemfunktionen
Rationale
AC-06(10) stops non-privileged users from running privileged functions, and AC-06(01) and (05) restrict security functions and privileged accounts to authorised roles. CM-05 restricts who can change the system configuration and system directories. AC-03(07) enforces role-based access control, and AC-02(07) administers privileged accounts in a role-based scheme (KONF.6.4.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.5 Dynamic access control in the system Dynamische Zugriffskontrolle im System
Rationale
AC-03(13) enforces attribute-based access control that weighs context, such as location or time. AC-16 attaches security attributes, such as data sensitivity, to information and users for access decisions. AC-02(11) enforces usage conditions on accounts, and AC-02(06) manages privileges dynamically.
Gaps
GS++ asks for access decisions that also weigh the state of the device, such as its health. Add device health to the attributes your access policy evaluates.
KONF.6.6 Keeping each account's data separate Getrennte Datenhaltung
Rationale
AC-03 enforces authorisations so that each account reaches only its own data. AC-06 limits each account to the data its tasks need. SC-50 treats tenants as separate security domains in software, each with its own access rights configuration (KONF.6.6.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.7 Privileged application functions Privilegierte Funktionen der Anwendung
Rationale
AC-03 enforces the application's authorisations for privileged functions, such as moderation or managing accepted certificates. AC-06(01) and (10) restrict privileged application functions to authorised roles, and AC-06(05) restricts privileged accounts.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.8 Access rights of the web server process Berechtigungen des Webserver-Prozesses
Rationale
AC-03 enforces file permissions that keep the web server process inside the web root and allow writes only to authorised subdirectories. AC-06 gives the process only the rights it needs. CM-07(02) stops it from running programs, such as shell commands, outside the intended interpreters.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.9 Access to code on web servers Zugriff auf Code
Rationale
AC-03 enforces access rules that keep source, configuration and credential files from being served. AC-22 has the organisation review its publicly accessible systems for nonpublic information and remove any it finds.
Gaps
GS++ asks web servers to block direct access to source files, such as code and configuration files. Write that rule into your web server's configuration as part of AC-03.
KONF.6.10 Listing directory contents on web servers Auflistung von Verzeichnisinhalten
Rationale
CM-07 turns off directory listing as an unneeded web server function, which hides the site's internal structure from attackers. CM-06 sets the web server to the most restrictive configuration that still lets it work.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.11 Restricting uploads to web servers Einschränkung von Uploads
Rationale
AC-03 allows uploads only from authenticated, authorised users and only into set storage locations. SC-06 uses quotas to limit upload size and storage use. SI-10 checks uploads, and SI-10(05) restricts inputs to approved formats, such as allowed file types.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.12 Moderation of public conference calls Konferenzmoderation 30%
Rationale
SC-15 sets rules for collaborative devices and applications, such as video conferencing. SC-15(04) shows who is currently in an online meeting, which lets a moderator notice unwanted participants.
Gaps
GS++ asks for moderation of public conference calls, so a moderator controls who speaks and can remove unwanted participants. Turn on the moderation features of your video conferencing application.
Mapped Controls
KONF.6.13 Dynamic access control in the application Dynamische Zugriffskontrolle in der Anwendung
Rationale
AC-03(13) enforces attribute-based access control in the application, using context such as location or device. AC-16 attaches security attributes, such as data sensitivity, to data and users for access decisions. AC-02(11) enforces usage conditions on accounts, and AC-02(06) manages privileges dynamically.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.14 Browser sandboxing Browser Sandboxing
Rationale
SC-39 keeps a separate execution domain for each process, so each browser process reaches only its own resources. Its discussion names sandboxing. SC-18(05) lets permitted mobile code, such as JavaScript, run only in confined environments.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.6.15 Virtualised browser environment Virtualisierte Browser-Umgebung
Rationale
SC-18(05) lets mobile code run only in confined virtual machine environments. SC-44 provides an isolated, virtualised environment where web content and URL requests run apart from the user's own system.
Gaps
GS++ asks for the whole browser to run in a virtualised operating system set aside for it, apart from the client. Use a remote-controlled browser system (ReCoBS) or a similar set-up.
KONF.6.16 Data exchange between virtualised clients Datenaustausch in der Virtualisierung
Rationale
AC-04 enforces approved information flows between virtual machines. SC-04 prevents unauthorised transfer of information through shared resources, such as shared memory or clipboards. SC-07 monitors and controls traffic at internal interfaces, such as the virtual networks between machines.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.1 Real-time malware scanner Echtzeitscanner 95%
Rationale
SI-03 configures malicious code protection to scan files in real time as they are downloaded, opened or executed. That gives the automatic check GS++ asks for when someone installs or opens a file.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.7.2 Regular malware scans Regelmäßige Scans 95%
Rationale
SI-03 configures malicious code protection to run periodic scans of the system, at a frequency the organisation defines. Those scans look for potential malicious code in the files already stored on the system.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.7.3 Host-based intrusion detection Host-basierte Angriffserkennung
Rationale
SI-04(23) puts host-based monitoring mechanisms on system components, such as servers and workstations. SI-07 checks the integrity of files and critical configuration on the host and detects unauthorised changes to them.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.4 Intrusion detection based on network traffic Angriffserkennung anhand von Netzverkehr 90%
Rationale
SI-04(04) monitors inbound and outbound traffic for unusual activity. SI-04(23) runs that monitoring on the host itself, so the system can spot port scans or connections to command-and-control servers.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.7.5 Alerting on possible malware Alarmierung
Rationale
SI-03 sends an alert to defined personnel or roles when it detects malicious code. SI-04(05) alerts defined personnel or roles when system-generated indicators show signs of compromise.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.6 Automatic updates of malware detection Automatische Updates 95%
Rationale
SI-03 updates malicious code protection mechanisms automatically as new releases appear. That keeps signatures and detection rules current against malware that changes to slip past known patterns.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.7.7 Regular testing of malware protection Regelmäßiger Funktionstest
Rationale
SI-03(06) tests malware protection with known benign code, such as the EICAR test file, and checks that detection and reporting work. SI-06 verifies at a set frequency that security functions operate correctly and alerts on failed checks.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.8 Dual-engine strategy for malware scanning Dual-Engine-Strategie
Rationale
SC-29 uses a diverse set of technologies for chosen components, such as different scan engines. PL-08(02) takes controls at a given layer from different suppliers, and SP 800-53 gives malware protection as its example. SI-03 lets signature-based and non-signature-based detection run side by side.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.9 Restricting application installation Einschränkung der Installation
Rationale
CM-11 sets and enforces policy on software installation by users, and CM-11(02) allows installation only with privileged status. CM-05 restricts the privileges to change the system, including installing software into system locations.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.10 Restricting application execution Einschränkung der Ausführung 90%
Rationale
CM-07(05) keeps a list of authorised software and blocks everything else from running. CM-07(02) prevents program execution that breaks the organisation's rules on software use.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.7.11 Restricting software libraries Einschränkung von Softwarebibliotheken
Rationale
CM-07(05) blocks all software by default and permits authorised software by exception, which can extend to libraries such as .dll and .so files. SI-07(12) verifies the integrity of code, including libraries, before it runs.
Gaps
GS++ asks for control over which software libraries may run. Extend your allow-list to libraries, such as .dll and .so files, as well as programs.
KONF.7.12 Restricting scripts Einschränkung von Skripten
Rationale
CM-07(02) and (05) let only authorised scripts run and block the rest. SC-18 defines which mobile code, such as JavaScript or VBScript, is acceptable and controls its use.
Gaps
GS++ asks for limits on what scripts may do, such as constrained language modes that restrict the system functions a script can call. Turn on features such as PowerShell Constrained Language Mode or Linux secure computing mode (seccomp).
KONF.7.13 Restricting system calls Einschränkung von Systemaufrufen
Rationale
AC-06 limits each process to the privileges its task needs, including the operating system resources an application may request. CM-07(06) runs software in a confined environment with limited privileges, as seccomp profiles do.
Gaps
GS++ asks for a filter on the system calls each application may make, such as seccomp on Linux. Set up those filters per application as part of confining software.
KONF.7.14 Code signing in the operating system kernel Code-Signierung im Betriebssystemkern
Rationale
CM-14 allows a component to install only after its signature from an approved certificate is verified. SI-07(15) authenticates code cryptographically before installation, and SI-07(12) verifies its integrity before it runs.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.15 Local firewall Lokale Firewall
Rationale
SC-07(12) puts host-based boundary protection, such as a local firewall, on each system. SC-07(05) denies traffic by default and allows it by exception. CM-07 restricts the ports, protocols and services a system uses to those it needs.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.7.16 Anti-exploit protection Anti-Exploit
Rationale
SI-16 protects memory from unauthorised code execution (KONF.7.16.1), for example with data execution prevention (DEP) and address space layout randomisation (ASLR). SI-07 protects the integrity of system files, as System Integrity Protection does, and SI-07(17) adds runtime protection against exploits.
Gaps
GS++ asks for operating system exploit protection beyond memory, such as Defender Exploit Guard and attack surface reduction rules. Turn these features on as part of each system's secure configuration.
KONF.8.1 Automatic check for security updates Automatische Überprüfung 95%
Rationale
SI-02 covers flaw remediation on IT systems. SI-02(02) uses automated mechanisms to check whether the available security updates are installed. SI-02(05) then installs security-relevant updates automatically (KONF.8.1.1).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.8.2 Automatic updates for applications Automatische Updates der Anwendung 95%
Rationale
SI-02 covers flaw remediation for the organisation's systems. SI-02(05) installs security-relevant software updates automatically on the system components the organisation defines, which can include each of its applications.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.9.1 Storage limit for the user environment Speicherplatzbegrenzung 85%
Rationale
SC-06 allocates resources such as storage to users and processes by quota. A quota on the user environment keeps its applications and services within their share of the disk, which leaves room for system services.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.9.2 Limiting host computing power Begrenzung der Hostleistung 85%
Rationale
SC-06 allocates processing resources by priority or quota. A host can use such quotas to cap computing power at the thresholds the organisation sets. One way is to limit the number of cores.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.9.3 Alternative components for critical functions Alternative Komponenten für kritische Funktionen
Rationale
SI-13 provides substitute components for critical functions, and SI-13(05) adds a way to fail over from active to standby components. CP-08 provides alternate telecommunications services, such as a mobile link when the wired network connection fails.
Gaps
GS++ gives redundant power supplies inside a system as an example. Plan them under SI-13 as substitute components for each critical function.
KONF.10.1 Baseline configuration for applications Grundkonfiguration für Anwendungen
Rationale
CM-02 documents a baseline configuration for the application and keeps it under configuration control. CM-02(03) retains previous versions of the baseline, so you can roll back (KONF.10.1.1). CM-06 establishes and documents the application's security settings.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.10.2 Cryptographic methods in applications Kryptographische Verfahren in Anwendungen
Rationale
SC-13 determines the cryptographic uses in the application and implements the required type of cryptography for each. SC-12 establishes and manages the keys that this cryptography depends on.
Gaps
GS++ asks for methods that follow recognised standards, such as BSI TR-02102, in line with its identity and access management requirements. SC-13 leaves the type of cryptography to you, so choose it from those standards.
KONF.10.3 Default credentials in applications Default-Zugangsdaten in Anwendungen 95%
Rationale
IA-05 has default authenticators changed before first use. That covers default passwords, and also the keys and certificates that an application accepts for sign-in by default.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.10.4 Disabling unneeded application functions Deaktivierung nicht benötigter Anwendungsfunktionen
Rationale
CM-07 configures the application to provide only essential functions and restricts unneeded modules, features and cloud connections. CM-06 sets the application's settings to the most restrictive mode consistent with operations.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.10.5 Checking the configuration against the baseline Überprüfung der Konfiguration
Rationale
CM-06 monitors the application's settings against the documented ones, and CM-06(01) verifies them with automated mechanisms (KONF.10.5.1). CM-03(07) reviews changes at a set frequency to find unauthorised ones.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.11.1 Authentication before access to protected data Authentifizierung vor dem Zugriff
Rationale
IA-02 authenticates the organisation's own users before they reach protected data. IA-08 authenticates external users, such as guests in portals or external participants in scheduled calls (KONF.11.1.1). IA-09 authenticates services and applications before they exchange data, as mutual TLS does (KONF.11.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.11.2 Waiting room for video conferences Warteraum
Rationale
IA-02 authenticates the organisation's own participants before they join a conference, and IA-08 authenticates external participants. SC-15(04) shows the current participants, so moderators can check who is present.
Gaps
GS++ suggests a waiting room, where a moderator checks each participant before letting them into the conference. Turn on that admission step in your conferencing tool.
KONF.11.3 Publication of domain information in DNS Veröffentlichung von Domain-Infomationen 75%
Rationale
SC-22 separates internal and external DNS roles. Records needed only inside the organisation then stay on internal servers, and the internet sees just the records of services meant for outside use.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.11.4 Protection against guessing access links Erraten von Zugriffslinks
Rationale
AC-07 limits consecutive failed attempts and then locks or delays further tries. The same pattern blocks the guessing of access links. SC-23(03) generates unique, random identifiers that resist brute-force guessing, and access links built that way resist it too.
Gaps
AC-07 counts failed logon attempts. GS++ asks for the same protection on links that grant access by themselves, such as meeting links. Add rate limiting or a CAPTCHA to requests for them.
KONF.11.5 Restricting unauthenticated telephony connections Einschränkung unauthentifizierter Anschlüsse
Rationale
AC-14 identifies the actions an unauthenticated endpoint may perform, such as emergency calls from a lift phone, and limits it to those. AC-04 enforces flow policies that restrict the destinations such endpoints can reach.
Gaps
The requirement targets telephony endpoints, such as public phones and fax machines in unsecured areas. Set the numbers and meetings each one may reach, and block the rest, such as premium-rate numbers.
KONF.11.6 Overview of signed-in connections Übersicht angemeldeter Verbindungen 45%
Rationale
AC-09 tells users about their previous logons when they sign in. AC-09(04) adds details such as location or device, so users can check that each sign-in is theirs.
Gaps
AC-09 reports at each logon. GS++ suggests an overview of the connections signed in right now, with details such as device name or IP address. Turn that view on in the application.
Mapped Controls
KONF.11.7 Restricting application interfaces Einschränkung von Schnittstellen
Rationale
AC-04 enforces approved flows to other applications and external peers, including zone transfers limited to authorised servers (KONF.11.7.1). CA-03 approves and documents each information exchange with other systems. CM-07 restricts enabled interfaces, extensions and cloud functions to those needed. SC-07 controls traffic at managed interfaces, as session border controllers do for telephony (KONF.11.7.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.11.8 Encryption of sensitive data at rest Verschlüsselung schützenswerter Daten (at-rest)
Rationale
SC-28(01) encrypts sensitive information at rest, such as credentials. IA-05(01) has passwords stored with an approved salted key derivation function, which GS++ accepts in place of encryption.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.12.1 Input validation Eingabevalidierung
Rationale
SI-10 checks the validity of inputs, and SI-10(06) prevents injection, as a web application firewall does. IA-05(02) validates certificates along the full path to a trust anchor, including revocation status. SC-18 controls mobile code, such as JavaScript and active content in Office files, and enforces content security policies. SI-07 verifies the integrity of loaded scripts, as Subresource Integrity does. SC-08 protects data in transit, and HSTS enforces that protection. IA-04 keeps identifiers unique, which blocks duplicates in the directory tree. CP-10(02) transaction recovery includes file system journaling.
Gaps
GS++ also asks web applications to send HTTP security response headers (KONF.12.1.10) and browsers to enforce the same-origin policy (KONF.12.1.3). Set both up in your server and browser configuration.
KONF.12.2 Encryption status of the current connection Verschlüsselungsstatus der aktuellen Verbindung 30%
Rationale
SC-08 protects the confidentiality and integrity of transmitted information. The browser's encryption indicator shows the user whether that protection is in place on the current connection.
Gaps
GS++ asks the browser to show the user whether the current connection is encrypted, for example with a padlock symbol. Turn that indicator on in your browser settings.
Mapped Controls
KONF.12.3 Cookies in web browsers Cookies 40%
Rationale
CM-07 limits the browser to the functions it needs. That includes storing cookies, which you can restrict to permitted sites, such as those on your intranet.
Gaps
GS++ addresses browser cookies by name, since they can hold sign-in tokens and personal data. Set a restrictive cookie policy in the browser configuration you deploy.
Mapped Controls
KONF.12.4 Storage of credentials in web browsers Speicherung von Zugangsdaten 90%
Rationale
IA-05(18) uses password managers to manage passwords and protect them. A dedicated password manager with browser integration, or browser storage protected by a master password, fits that enhancement.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.12.5 Autofill of data in web browsers Auto-Vervollständigung von Daten 50%
Rationale
CM-07 limits the browser to the functions it needs, which lets you restrict autofill. Pages then see just the data the user types into a form.
Gaps
GS++ addresses browser autofill by name, because a page can read filled-in fields before the user sends the form. Restrict it through your browser policy.
Mapped Controls
KONF.12.6 Persistent browser history Browser-Historie
Rationale
CM-07 switches off persistent history as an unneeded function. SI-14(02) deletes information once it has served its purpose, such as clearing the history when the browser closes.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.12.7 Extended attributes on file servers Erweiterte Attribute
Rationale
AC-16 associates security attributes with information in storage. Extended attributes store them as metadata on each file, for example access rights and status flags. AC-03 enforces the access rights held there.
Gaps
GS++ asks file servers to turn on extended attributes in the file system, for example through Samba on Linux or NTFS on Windows. Set this when you build each server.
KONF.12.8 Joining conferences with video and audio off by default Teilnahme per Default ohne Bild und Ton 70%
Rationale
SC-15 prohibits remote activation of cameras and microphones in collaborative applications, so only the participant can switch them on. It also shows when these devices are in use.
Gaps
GS++ asks conferencing tools to have camera and microphone off when a participant joins. Set that default in the tool, so users switch them on when they choose.
Mapped Controls
KONF.12.9 No covert recording in video conferences Keine heimliche Aufzeichnung
Rationale
SC-15 shows participants clearly when collaborative devices and applications are in use. PT-05(01) and SC-42(04) tell people when their personal data is being collected, for example by a recording.
Gaps
GS++ asks the tool to tell every participant about a recording, including those who join late. Switch off any way to record a conference covertly.
KONF.12.10 Cookie attributes in web applications Cookie-Attribute
Rationale
SC-08 protects cookies in transit, and the Secure attribute enforces that by keeping them on HTTPS. SC-23 protects session authenticity against hijacking and cross-site request forgery, which the HttpOnly and SameSite attributes support.
Gaps
GS++ names the cookie attributes, such as Secure, HttpOnly and SameSite. Turn them on in the application or web server configuration.
KONF.12.11 Anonymous or pseudonymous communication Anonyme oder Pseudonyme Kommunikation 30%
Rationale
SC-30 uses concealment techniques to hide identifying details from the other party, such as the caller's identity or internal extension numbers. SC-30(05) conceals system components, such as the network source of a connection.
Gaps
GS++ suggests sending the other party a pseudonym, or withholding the caller ID. Turn on caller ID suppression, or send a general number in place of the extension.
Mapped Controls
KONF.12.12 Connection log for users Verbindungsprotokoll
Rationale
AU-02 names connections as an event type to log, and AU-12 generates the records. AU-03 sets what each record holds, such as the time, duration, peer and direction of a connection.
Gaps
GS++ asks the telephony application to show each user a log of their own calls. Turn on a call list each user can see, for example in the phone app.
KONF.12.13 Fax transmission report Sendebericht
Rationale
AU-12 generates a record of each fax transmission. AU-10 provides evidence that a message was sent, which a fax transmission report gives as legal proof.
Gaps
GS++ suggests details for the report, such as the number of pages sent and the status the call ended with. Set the fax application to include them.
KONF.12.14 False information in DNS answers DNS-Falschinformationen
Rationale
SC-20 has authoritative servers add origin authentication and integrity data to their answers. SC-21 has resolvers verify the origin and integrity of the answers they receive, including those from upstream servers.
Gaps
GS++ asks you to switch off answer rewriting, such as redirecting unknown names to advertising pages. Check both your own DNS servers and the upstream servers they use.
KONF.13.1 Filtering harmful messages Filtern schädlicher Nachrichten
Rationale
SI-03 detects and removes malicious code in messages and attachments at entry points, such as mail gateways. SI-08 detects and acts on unsolicited messages at entry and exit points (KONF.13.1.1). SC-18(04) prevents the automatic execution of active content in messages (KONF.13.1.2).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.13.2 Authenticity of messages Authentizität von Nachrichten
Rationale
SI-08 checks incoming mail at entry points and acts on spoofed or unauthenticated messages. AU-10(02) validates the binding of the sender's identity to the message. SC-08(01) uses cryptography to detect changes to messages in transit.
Gaps
GS++ asks mail systems to verify the sending authorisation and the server signature of incoming mail. Turn on Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) checks at your mail gateway.
KONF.13.3 Cryptographic signature of the mail server Kryptographische Signatur des Mailservers
Rationale
AU-10(01) binds the sending domain's identity to each outgoing message. SC-08(01) lets recipients detect changes to messages in transit. SC-13 implements approved cryptography for the signature.
Gaps
GS++ asks the mail server to sign outgoing mail, for example with DomainKeys Identified Mail (DKIM). Turn on DKIM signing for each domain you send from.
KONF.13.4 Cryptographic signature by users Kryptographische Signatur durch Nutzende
Rationale
AU-10 provides evidence that a user sent a message, through a digital signature that recipients can verify. SC-17 issues the public key certificates that S/MIME needs, under a certificate policy.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.13.5 Publication of the sending authorisation in DNS Publikation der Sendeberechtigung 35%
Rationale
SI-08 provides spam protection at entry and exit points. A published sender policy lets receiving spam filters, the organisation's own among them, reject mail that spoofs its domain.
Gaps
GS++ asks you to publish in DNS the servers allowed to send mail for your domain, for example with a Sender Policy Framework (SPF) record. Make that policy strict, as KONF.13.5.1 asks.
Mapped Controls
KONF.13.6 Publication of the server signature in DNS Publikation der Serversignatur 50%
Rationale
SC-12 manages cryptographic keys, including the distribution of public keys. SC-12(03) distributes asymmetric keys, such as the public key for DomainKeys Identified Mail (DKIM), which receiving servers look up in DNS.
Gaps
GS++ asks you to publish the public key of your server signature in DNS. Add a DKIM record for each domain and signing key.
Mapped Controls
KONF.13.7 TLS reports for email TLS-Reports
Rationale
AU-06 reviews and analyses the reports at a set frequency for unusual activity. SI-04 uses them as monitoring information to detect attacks on mail transport, such as downgrade or interception attempts.
Gaps
GS++ suggests reviewing TLS reports (TLS-RPT), which other mail operators send about problems delivering mail to you over TLS. Add them to the records you review under AU-06.
KONF.13.8 Email authentication reports (DMARC) DMARC-Reports
Rationale
AU-06 reviews and analyses the reports for unusual activity, at a set frequency or when they arrive. SI-04 uses them as monitoring information to detect misuse of the domain, such as failed authentication checks.
Gaps
GS++ suggests reviewing the DMARC reports that receiving mail servers send about mail from your domain. Add them to the records you review under AU-06, ideally with automated analysis.
KONF.13.9 Publication of the email authentication policy (DMARC) Publikation der DMARC-Richtlinie 35%
Rationale
SI-08 provides spam protection at entry and exit points. A published DMARC policy tells receiving spam filters how to treat mail that fails authentication for the organisation's domain.
Gaps
GS++ asks you to publish your DMARC policy as a record in DNS. Add one for each of your domains.
Mapped Controls
KONF.13.10 Authenticating server certificates through DNS Authentifizierung der Server-Zertifikate über DNS
Rationale
SC-17 obtains certificates from approved providers only, and Certificate Authority Authorization (CAA) records name those providers in DNS. SC-21 validates DNSSEC signatures on DNS answers, which DNS-based Authentication of Named Entities (DANE) relies on. SC-23(05) allows only defined certificate authorities for protected sessions.
Gaps
GS++ asks mail servers to check server certificates through DNS, with DANE or CAA records. Publish these records for your mail domains and turn on DANE checks in your mail servers.
KONF.13.11 Strict transport security for mail (MTA-STS) MTA-STS
Rationale
SC-08(01) enforces encrypted transmission between mail servers, which blocks a downgrade to plain text. SC-23 protects session authenticity against a false server intercepting the mail.
Gaps
GS++ asks for Mail Transfer Agent Strict Transport Security (MTA-STS), which tells sending servers to deliver to your domain over TLS only. Publish an MTA-STS policy for each mail domain.
KONF.14.1 Encryption in transit Verschlüsselung beim Transport
Rationale
SC-08(01) encrypts information in transit over networks, for example with TLS. SC-13 implements cryptography to the recognised standard the organisation sets. CM-07 disables unencrypted and vulnerable protocols (KONF.14.1.1).
Gaps
GS++ also suggests end-to-end encryption (KONF.14.1.2). SC-08 leaves you to choose where encryption ends, so decide which communication needs end-to-end protection.
KONF.14.2 Source port randomisation for DNS Source Port Randomisierung
Rationale
SC-21 protects the integrity of resolver answers against spoofing and cache poisoning. SC-30(02) introduces randomness into operations, such as random source ports for DNS queries.
Gaps
GS++ asks DNS servers to randomise the source ports of their queries, as RFC 5452 describes. Check that your resolver software has this switched on.
KONF.14.3 Iterative answers to DNS queries from the internet Iterative Beantwortung
Rationale
SC-22 separates the external, authoritative roles of DNS servers from internal, recursive ones. CM-07 disables recursion for clients on the internet, so internet-facing servers answer their queries iteratively.
Gaps
GS++ asks internet-facing DNS servers to answer queries iteratively. SP 800-53 reaches that through role separation and disabled recursion, so check the setting on each such server.
KONF.14.4 Caching frequently used data on mobile devices Caching 35%
Rationale
SC-36 distributes processing and storage across several locations, and a local cache on the mobile device is one of them. The cache keeps frequently used data available when the network fails.
Gaps
GS++ suggests caching frequently used data on the device, for speed and to keep working during network outages. Turn on caching in the applications where that helps.
Mapped Controls
KONF.14.5 Timeout for network connections Zeitüberschreitung von Netzverbindungen
Rationale
SC-10 terminates network connections at the end of a session or after a period of inactivity. AC-12 terminates user sessions automatically on defined conditions, such as idle time.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
KONF.15.1 Limiting storage space per account or tenant Begrenzung des Speicherplatzes 85%
Rationale
SC-06 allocates storage by quota to each account or tenant. A quota, such as 5 or 10 GB, stops a single account or tenant from using up the storage that all of them share.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.15.2 Limiting computing power per account or tenant Begrenzung der Rechenleistung 85%
Rationale
SC-06 allocates processing resources by priority or quota to each account or tenant. A directory service, for example, can cap the time that any one search may take.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.15.3 Protection against denial of service Schutz gegen Denial of Service 90%
Rationale
SC-05 protects against denial-of-service events or limits their effects. SC-05(02) manages capacity and redundancy, for example with load balancers, and SC-05(03) detects attacks as they happen.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
Mapped Controls
KONF.15.4 Overcommitment of virtualised resources Überbuchung von virtualisierten Ressourcen 65%
Rationale
SC-06 allocates resources by priority or quota. Fixed quotas can reserve real capacity for each virtual instance, so the hardware can deliver every resource it has promised.
Gaps
GS++ suggests switching off overcommitment, where the platform hands out more virtual resources than the hardware has. Set your virtualisation platform to reserve real capacity for each instance.
Mapped Controls
DEV.1.1 Development: procedures and rules Verfahren und Regelungen
Rationale
SA-01 sets policy and procedures for system acquisition and development, documents them and gives them to the roles that need them (DEV.1.1.1, DEV.1.1.3). SA-03 defines security roles across the development life cycle and names the people who hold them (DEV.1.1.2). SA-15 has development follow a documented process that addresses security.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.1.2 Development: regular review Regelmäßige Überprüfung
Rationale
SA-01 reviews and updates the development policy and procedures at a set frequency and after defined events, such as a serious security incident. SA-15 reviews the development process, its standards and its tools at a set frequency.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.2.1 Security by design in the architecture Security by Design Architektur
Rationale
PL-08 develops a security architecture that describes how the system protects information. SA-08 applies security engineering principles to the design and development of the system. SA-17 has the developer produce a security architecture and design that allocates security functions to components. SA-11(02) runs threat modelling during development, the method GS++ suggests.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.2.2 Documenting the software architecture Dokumentation der (Software-)Architektur
Rationale
PL-08 documents the system's security architecture, including its dependencies on external systems and services. SA-17 has the developer produce a design specification that describes the components, their interfaces and how the security functions work together.
Gaps
GS++ asks for the architecture documents to cover the data model as well. Add it to the architecture and design documents you keep under PL-08 and SA-17.
DEV.2.3 Running with minimal privileges Ausführbarkeit mit minimalen Rechten
Rationale
AC-06 lets the application run with only the access its tasks need. SA-08(14) applies the least privilege principle in design, and SA-17(07) structures the software so access can be controlled with least privilege.
Gaps
GS++ asks the application to keep working with reduced functions when a permission is withheld, known as graceful degradation. Build and test for it. A photo viewer, for example, still shows saved images when the user refuses camera access.
DEV.2.4 Restricting write access to source code Einschränkung Zugriffs auf Quellcode
Rationale
AC-06 gives write access only to the developers and maintainers whose tasks need it. CM-05 restricts who can make changes, and CM-05(06) limits the privileges to change software in libraries. SA-10 controls the integrity of changes to configuration items such as source code.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.2.5 Restricting access to application credentials Einschränkung des Zugriffs auf Zugangsdaten
Rationale
AC-03 enforces access rules on the vault or store that holds the credentials, and AC-06 limits reading and writing them to those who need it. IA-05(07) keeps unencrypted static credentials out of source code, and IA-05 protects authenticator content.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.2.6 Resistance to common attack patterns Widerstandsfähigkeit gegen gängige Angriffsmuster
Rationale
SI-10 validates input, and SI-10(06) prevents injection by checking input for embedded commands (DEV.2.6.1). SI-15 checks output against the expected content (DEV.2.6.2). SI-16 protects memory against exploits such as buffer overflows. SA-15 builds secure coding standards into the development process. SA-11(01) and (08) find common flaws with static and dynamic analysis.
Gaps
GS++ asks for output encoding (DEV.2.6.2). SI-15 checks output against the expected content, so add encoding that suits each output context to your secure coding standards.
DEV.3.1 Blocking replay attacks Replay-Angriffe
Rationale
IA-02(08) makes authentication resistant to replay, for example with nonces or challenges. SC-23 protects the authenticity of sessions against false or replayed information inserted into them.
Gaps
GS++ asks for replay protection on every request the application accepts, such as API calls from other systems. Use one-time identifiers or message authentication codes on those requests as well as at sign-in.
DEV.3.2 Error-handling routines Routinen zur Fehlerbehandlung
Rationale
SC-24 makes the application fail to a known state when defined failures occur. SI-10(03) makes it behave predictably when invalid input arrives. SI-11 generates error messages that give the information needed for corrective action.
Gaps
GS++ asks you to handle each exception close to its source and to add a general routine that catches unexpected errors. Write both into your coding standards and test them.
DEV.3.3 Disabling output of sensitive data in error messages Deaktivierung der Ausgabe schützenswerter Daten durch Fehlermeldungen
Rationale
SI-11 keeps exploitable information out of error messages and reveals them to defined roles only. IA-06 obscures feedback during authentication, so a failed sign-in keeps secret whether the account exists.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.3.4 Password hashing Passwort-Hashing
Rationale
IA-05(01) has the application store passwords with an approved salted key derivation function, the hash and salt GS++ asks for. SC-13 implements approved cryptography for the hash itself.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.4.1 Informing users about security-critical events Nutzerinformation bei kritischen Ereignissen 55%
Rationale
AC-09 tells users about their previous logon when they next sign in. AC-09(03) reports changes to the security settings of their account, and AC-09(04) adds details such as a new location or device.
Gaps
GS++ asks you to alert users when the event happens, for example by email after a password reset or a sign-in from a new device. AC-09 notifies them at their next logon.
Mapped Controls
DEV.4.2 Integrating external software from trusted sources Einbindung externer Software
Rationale
CM-10(01) restricts the use of open-source software. SA-09 holds providers of external services and interfaces to the organisation's security requirements. SR-04 documents where each component comes from, so unknown sources show up. SR-05 uses acquisition methods that keep out risky components, and SR-06 assesses suppliers and the components they provide.
Gaps
GS++ asks you to forbid components and interfaces from unreliable or unknown sources. Decide which sources you trust, and make your provenance and supplier checks block the rest.
DEV.4.3 Software components (software bill of materials) Softwarebestandteile (SBOM)
Rationale
CM-08 keeps an inventory of software components at the level of detail needed, which is what a software bill of materials holds. SR-04 documents the provenance of each component, including its composition and dependencies.
Gaps
GS++ asks for a software bill of materials before each release, in a format such as BSI TR-03183-2. Produce it from your CM-08 inventory, for example with software composition analysis in your build pipeline.
DEV.4.4 Integrity of external software Integrität externer Software
Rationale
SI-07(06) and (15) check external artifacts with cryptography, such as hashes and signatures. SR-04(03) validates that components are genuine and unaltered. SR-10 inspects components to detect tampering, such as injected malicious code. SR-11 detects and prevents counterfeit components.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.4.5 Security updates for external software Updates externer Software
Rationale
RA-05 scans the application and its components for known vulnerabilities, as software composition analysis does. SA-15(07) has the developer run automated vulnerability analysis. SI-02 identifies flaws and installs the security updates for bundled components, which GS++ asks for before each release.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.4.6 Compiler options for security functions Compileroptionen
Rationale
SA-15 documents the development tools with their options and configurations, and reviews them. SI-16 protects memory from unauthorised code execution, which compiler options such as stack canaries and control-flow integrity provide.
Gaps
GS++ asks you to switch on the compiler's security options before each release, and the matching options for interpreted languages. Make them part of the tool settings you document under SA-15.
DEV.4.7 Deterministic binary code (reproducible builds) Deterministischer Binärcode
Rationale
SA-10(04) compares newly generated object code with earlier versions, and SA-10(05) keeps the build data tied to the master copies. SA-15 documents the tools, options and configurations used to build the software, which describes the build environment.
Gaps
GS++ asks for a documented build that turns the same source into bit-for-bit identical binaries. Describe the build environment exactly and remove variable inputs, such as timestamps.
DEV.4.8 Documenting default credentials Default-Zugangsdaten
Rationale
SA-05 has administrator documentation describe secure installation and configuration, including any default credentials. IA-05(05) has developers supply unique authenticators or change the defaults before delivery.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.4.9 Default settings that follow security by default Voreinstellungen nach dem Prinzip "Security by Default"
Rationale
SA-04(05) has the product delivered with its security configurations set as the default. SA-08(23) applies the secure defaults principle to the configuration the product ships with.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.4.10 Logging code changes Protokollierung von Codeänderungen
Rationale
CM-03 documents change decisions and keeps records of each change for a set period. SA-10 documents and controls changes to configuration items such as source code.
Gaps
GS++ asks each record to show the time, the content, the author and the reason for the change. Set your version control and change records to capture all four.
DEV.4.11 Testing source code changes Test bei Änderungen am Quellcode
Rationale
CM-03(02) tests, validates and documents changes before they go live. CM-04 analyses each change for its security impact, and CM-04(01) does so in a separate test environment. SA-11 has the developer run unit, integration, system and regression tests, with static and dynamic analysis under SA-11(01) and (08).
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.5.1 Committing to a period for security updates Verankerung des Zeitraums für Updates 35%
Rationale
SA-22 deals with components whose developer or vendor has stopped supplying patches and updates. A committed update period makes that end of support known in advance.
Gaps
GS++ asks you to commit to security updates for a minimum period, counted from a set date such as first release. Set this commitment for each product yourself.
Mapped Controls
DEV.5.2 Informing customers of the update period Information über Zeitraum für Updates 30%
Rationale
SA-05 has the developer provide documentation for users and administrators. That documentation can state how long the product receives security updates and how customers obtain them.
Gaps
GS++ asks you to tell customers how long you will supply security updates and how they get them. Put both in the documentation you deliver under SA-05.
Mapped Controls
DEV.5.3 Integrity checks for installation and update files Integritätsprüfung
Rationale
SA-10(01) has the developer enable integrity verification of software and updates, such as published hashes, and SA-10(06) makes distributed updates match the master copies. SA-05 user documentation explains how to use security functions, such as checking a file's integrity.
Gaps
GS++ asks you to publish checksums over an authenticated channel, such as a website with an X.509 certificate. Tell users there how to check installation, update and patch files.
DEV.6.1 Approval for use under change and test procedures Freigabe nach Änderungen und Tests
Rationale
CM-03 reviews proposed changes, approves or rejects them and implements only the approved ones. SA-10 has the developer implement only changes the organisation has approved, so each release goes into use with an authorisation.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.7.1 Secure deployment Sichere Bereitstellung
Rationale
CM-03 implements approved changes in production under change control, and CM-03(03) automates their deployment. SA-10 has the developer perform configuration management during implementation and operation of the system.
Gaps
SP 800-53 states this more generally than GS++. Check the controls against BSI's wording.
DEV.7.2 Certificate monitoring for the application's domains Zertifikatsmonitoring
Rationale
SC-17 obtains certificates under a certificate policy or from approved providers, so a certificate from anywhere else stands out. SI-04 monitors for indicators of attack, which can include new certificates for the organisation's domains in Certificate Transparency logs.
Gaps
GS++ asks you to watch Certificate Transparency logs for new certificates issued for every domain the application uses. Add those logs to the sources your SI-04 monitoring covers.
The German titles are the source's own wording, from BSI's Anwenderkatalog Grundschutz++ of 29 October 2026, by the Bundesamt für Sicherheit in der Informationstechnik, licensed under CC BY-SA 4.0. OSA translated BSI's titles into English and summarised the requirements in the rationale and gaps. Where BSI gives two requirements the same title, the English title adds the subject. OSA made this mapping independently of BSI and shares it under the same licence.
Methodology and Disclaimer
This coverage analysis maps from BSI Grundschutz++ clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.
Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.
This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.