Note: For security reasons, I don’t provide a Word, LibreOffice, or RTF document. You can simply copy and format the questions as text.
Project Details
- Identification Number:
- Project’s Name:
- Client/Requester:
- Product Owner/Project Manager:
Architecture Description
- Purpose of the System:
- Production Server Diagram
- Code and Function of Involved Systems and Microservices:
Security Measures
- How are these systems secured/protected?
- Which network protocols are used?
- Which authentication methods are applied?
- How is user management handled and who’s responsible for it?
- Which permission groups are set up and for what purpose?
- Which data transfers and interfaces are used and what security measures are implemented?
- Are preventive security measures taken, e.g., backups and emergency measures?
- Who’s responsible for regularly testing the system restoration from backup?
- How often is testing of system restoration from backup performed?
- Are changes (data, configuration, etc.) traceably documented?
- Are controls/spot checks carried out, and if so, where, when, and by whom?
- Are there compensating control actions that enable early risk detection?
- Attachments such as network diagram and permission concept
Data Classification
What types of data are processed?
How critical are the data for other business processes of the company?
How critical is it from the customer’s perspective if data is unintentionally made public, stolen, altered, or deleted?
Are personal data stored in other systems?
Can the system’s function be fulfilled without processing personal data?
The following types of data are collected and processed:
- Personal data (customer/employee data)
- Business-sensitive information
- Public data
System Access
| From the corporate/internal network | From the Internet via VPN | From the Internet without VPN | |
|---|---|---|---|
| Internal employees | Yes/No | Yes/No | Yes/No |
| External service providers | Yes/No | Yes/No | Yes/No |
| Business partners | Not possible | Yes/No | Yes/No |
| Customers | Not possible | Not possible | Yes/No |
IT System Locations
- DMZ: Protected network with access from LAN and Internet
- Internal network
- Externally hosted systems: Description of the data center or public cloud
Detailed Risk Assessment
These risks must be coordinated with both the client and the data protection officer and information security officer. And these measures must be considered in the project plan.
| Area | Planned Security Measures | Residual Risks | Assessment of Residual Risk |
|---|---|---|---|
| Data | |||
| Systems | |||
| Network | |||
| Interfaces | |||
| Users |
Comments for Approval
The project has been reviewed in advance and, subject to the implementation of the required measures, is
- approved
- not approved
If technical changes occur after the risk assessment date, the risk assessment must be repeated.
Signatures
| Date, Signature | Date, Signature | Date, Signature |
| Project Responsible | Data Protection Officer | Information Security Officer |
License
This work is marked CC0 1.0 Universal
