> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/regulatory-framework-mappings/german-remote-maintenance-bsi-cs-108/bsi-rules-on-remote-maintenance-in-industrial-environments.md).
# BSI Rules on Remote Maintenance in Industrial Environments
BSI-CS 108, Version 1.00
### To get Dispel's complete mapping, download our document here:
{% file src="/files/8PRPyXTeDAjzT0Xl29ZZ" %}
### Introduction
The German Federal Office for Information Security (Bundesamt für Sicherheit in der Informationstechnik, or “BSI”) sets security standards and recommendations for federal agencies; corporations, institutions and foundations under public law; as well as public companies that are majority owned by the federal government and that provide IT services for the federal administration. Private companies often also use BSI recommendations for their own cybersecurity planning.
#### BSI, Industrial Control System Security, & Remote Access
The BSI has several documents focusing on remote access, divided into two primary categories: IT and OT.
The IT-focused BSI-CS 054 *Grundregeln zur Absicherung von Fernwartungszugängen* addresses allowing remote access within environments ranging across home networks, small businesses, enterprise, and government authorities.\[1]
Because OT environments are unique in their device types, maintenance windows, network configurations, and the risk impact of an attack against critical infrastructure the BSI also issues two recommendations for OT access. The more broad *ICS Security Compendium*\[2] draws heavily upon IEC 62443, VDI/VDE 2182, NERC CIP, and U.S. Department of Homeland Security Best Practices. Focusing specifically on remote access, the BSI has also issued particular recommendations in BSI-CS 108 *Remote Maintenance in Industrial Environments*.\[3] Because of its singular focus on remote access, we address our alignment with BSI-CS 108 in this document. This complements Dispel’s other alignments with [IEC 62443](https://docs.dispel.com/map/iec-62443/iec-62443), [NERC CIP](https://docs.dispel.com/map/overview), [DHS TIC](https://docs.dispel.com/map/dhs-tic/overview), and other cybersecurity frameworks.
### BSI-CS 108 Categories
The BSI recommendations are broken into the following five categories:\[4]
1\. Architecture
2\. Secure communications
3\. Authentication mechanisms
4\. Organizational requirements
5\. Miscellaneous
In this document we provide a 1:1 mapping of the technical requirements within each category against Dispel capabilities.
***
\[1] BSI, *Grundregeln zur Absicherung von Fernwartungszugängen*. November 11, 2018. Version 2.0.
\[2] BSI, *ICS Security Compendium*. 2023. Version 1.23.
\[3] BSI, *Remote maintenance in industrial environments*. 2015. Version 1.00.
\[4] *Ibid*., 1-3.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dispel.com/regulatory-framework-mappings/german-remote-maintenance-bsi-cs-108/bsi-rules-on-remote-maintenance-in-industrial-environments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
