1. Header Information
Step 1: Enter basic information about your service or application. This includes what it’s called, who owns it, what it does, etc.
2. General Notes
Step 2: Provide additional context on how your service is structured. Include high-level diagrams, architectural notes, or important references if available.
3. Data Dictionary
Step 3: Document the types of data your service handles. For example, user emails, credentials, or logs. Also include how the data is classified (e.g. PUBLIC, INTERNAL, CONFIDENTIAL).
| Data Type | Description | Classification | Actions |
|---|
4. Risk Table
Step 4: Identify potential impacts to Confidentiality, Integrity, or Availability (CIA). Consider how a breach would affect reputation, productivity, and finances. Estimate the likelihood (e.g., 0.1/year for very low, 1/year for moderate, etc.).
| Risk Aspect | Reputation Impact | Productivity Impact | Financial Impact | Likelihood (1/yr) | Rationale | Actions |
|---|
Example:
Confidentiality (C), Integrity (I), Availability (A)
Reputation: LOW, MED, HIGH, MAX
Productivity: LOW, MED, HIGH, MAX
Finances: LOW, MED, HIGH, MAX
Likelihood: e.g. Very Low (~0.1/yr), Low (~0.5/yr), Medium (1/yr),
etc.
5. Recommendations
Step 5: Suggest action items or next steps to improve security or address any identified risks.