msolarczekandClaude Opus 5
c8e6f30a27
Unveränderter Stand von certvia/dev (a48c5fb) plus Craftvia-Spezifikation und Brandbook unter docs/craftvia/. ISMS-Module werden im Folgecommit entfernt. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
68 lines
2.6 KiB
Markdown
68 lines
2.6 KiB
Markdown
# Access & Visitor Management (physical)
|
|
|
|
| Document information | Value |
|
|
|-----------------------|------|
|
|
| Document type | Procedure instruction (VA-17) |
|
|
| Scope | {{ISMS_SCOPE}} |
|
|
| Organisation | {{ORG_NAME}} |
|
|
| Process owner | {{ROLE_IT_LEAD}} |
|
|
| Approved by | {{ROLE_ISB}} |
|
|
| Version | {{DOC_VERSION}} |
|
|
| Date | {{DOC_DATE}} |
|
|
| Status | {{DOC_STATUS}} |
|
|
|
|
<!-- FULFILLS 3.1.1-S1, 3.1.1-S2, 3.1.1-S3, 3.1.1-S4, 3.1.1-S5, A.7.1-1, A.7.11-1, A.7.12-1, A.7.2-1, A.7.3-1, A.7.4-1, A.7.5-1, A.7.6-1, A.7.7-1, A.7.8-1 | POLICY R07 -->
|
|
|
|
## 1. Purpose
|
|
|
|
This procedure governs the granting and revocation of physical access rights, visitor management as well as the handling of utilities in security zones. It operationalises the associated policy ({{LINK:R07}}).
|
|
|
|
## 2. Scope
|
|
|
|
Applies within the ISMS scope ({{ISMS_SCOPE_DESCRIPTION}}) for all sites and security zones.
|
|
|
|
## 3. Trigger
|
|
|
|
Joining/leaving/role change, visit, change to the zone concept, regular review.
|
|
|
|
## 4. Inputs
|
|
|
|
- Zone/security concept ({{LINK:BASELINE}}, BL-PHY-01/02)
|
|
- Personnel/visitor notification
|
|
- Existing access authorisations
|
|
|
|
## 5. Process
|
|
|
|
1. Access rights to security zones are requested, approved and revoked via {{TOOL_TICKET}} (least-privilege principle).
|
|
2. Visitors are registered, identified and escorted in areas requiring protection.
|
|
3. Utilities, keys and badges are issued, taken back and documented.
|
|
4. Access authorisations are reviewed regularly ({{REVIEW_CYCLE}}) and adjusted without delay upon leaving/change.
|
|
|
|
## 6. RACI
|
|
|
|
| # | Step | R (Execution) | A (Accountable) | C (Consulted) | I (Informed) |
|
|
|---|---------|------------------|------------------|-----------------|----------------|
|
|
| 1 | Grant/revoke access rights | {{ROLE_IT_LEAD}} | {{ROLE_IT_LEAD}} | {{ROLE_ISB}} | - |
|
|
| 2 | Register/escort visitors | Reception/business unit | {{ROLE_IT_LEAD}} | {{ROLE_ISB}} | - |
|
|
| 3 | Manage utilities/keys | {{ROLE_IT_LEAD}} | {{ROLE_IT_LEAD}} | - | - |
|
|
| 4 | Review access authorisations | {{ROLE_ISB}} | {{ROLE_ISB}} | {{ROLE_IT_LEAD}} | - |
|
|
|
|
## 7. Result & evidence
|
|
|
|
Up-to-date access authorisations and visitor logs. Evidence is referenced in the central evidence register ({{LINK:NACHWEISREGISTER}}).
|
|
|
|
## 8. Key performance indicators (KPI)
|
|
|
|
- Up-to-dateness of the access list
|
|
- Overdue recertifications of access rights
|
|
- Completeness of visitor logs
|
|
|
|
## 9. Related documents
|
|
|
|
- Associated policy: {{LINK:R07}}
|
|
- Authorisation procedure (logical analogue): {{LINK:VA-03}}
|
|
- Technical security baseline: {{LINK:BASELINE}}
|
|
- ISA mapping matrix: {{LINK:ISA_MAPPING}}
|
|
|
|
<!-- Erfüllt die oben unter FULFILLS gelisteten Anforderungen; Kopplung in mapping.json. Im Lesemodus nicht sichtbar. -->
|