1.2.5 Services, protocols, ports inventoried and justified
All services, protocols, and ports allowed are identified, approved, and have a documented business need.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Last review date and reviewer · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Inventory of allowed ports, protocols, services · Policy repository / GRC workspace
- Business justification document per entry · Policy repository / GRC workspace
- Risk acceptance for insecure protocols · Policy repository / GRC workspace
- Compensating controls documentation · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- No justification for legacy protocols
- Insecure protocols allowed without controls
- Inventory not reviewed annually
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet1.2.4 Data flow diagram of account data · 1.2.6 Security features for insecure services defined