Skip to content

Improve language in SCS-121-w1 #979

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mbuechse merged 4 commits into from
Sep 10, 2025
Merged

Improve language in SCS-121-w1 #979

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
05277ff
A typo and a few wording changes.
garloff Sep 2, 2025
82ac396
One more ...
garloff Sep 2, 2025
1d2ca96
fix yet another typo
depressiveRobot Sep 2, 2025
1bce0d6
Minor rephrasing
mbuechse Sep 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions Standards/scs-0121-w1-Availability-Zones-Standard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ supplements:

The standard will not preclude small deployments and edge deployments, that both will not meet the requirement for being divided into multiple Availability Zones.
Thus multiple Availability Zones are not always present.
Somtimes there can just be a single Availability Zones.
Sometimes there can just be a single Availability Zone.
Because of that, there will be no automated tests to search for AZs.

## Required Documentation
Expand All @@ -24,11 +24,11 @@ For each deployment, that uses more than a single Availability Zone, the CSP has
4. The redundancy in external connection within each AZ MUST be documented.
5. The redundancy in core routers within each AZ MUST be documented.

All of these requirements will either not change at all like the fire zones or it is very unlikely for them to change like redundant internet connection.
Because of this documentation must only be provided in the following cases:
After the initial setup, these requirements typically do not change at all (like the fire zones) or are very unlikely to change (like redundant internet connection).
Because of this, documentation needs to be provided only in the following cases:

1. When a new deployment with multiple AZs should be tested for compliance.
2. When there are physical changes in a deplyoment, which already provided the documentation: the changes needs to be documented and provided as soon as possible.
1. When a new deployment with multiple AZs should be tested for compliance initially.
2. When there are physical changes in a deployment that already provided documentation: the changes need to be documented and provided as soon as possible.

### Alternative Documentation

Expand All @@ -37,5 +37,5 @@ It is still required to document the existence of fire zones and the correct con

## Physical Audits

In cases where it is reasonable to mistrust the provided documentation, a physical audit by a natural person - called auditor - send by e.g. the [OSBA](https://osb-alliance.de/) should be performed.
The CSP of the deployment, which needs such an audit, should grant access to the auditor to the physical infrastructure and should show them all necessary IaaS-Layer configurations, that are needed to verify compliance to this standard.
When reasons exist to mistrust the provided documentation, a physical audit by a natural person - called auditor - sent by e.g. the [OSBA](https://osb-alliance.de/) should be performed.
The CSP of the deployment in need of such an audit should grant access for the auditor to the physical infrastructure and should show them all necessary IaaS-Layer configurations that are needed to verify compliance to this standard.