Skip to content
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.

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

Create a standard structure for Threats and Controls #26

Open
Tracked by #47
ColinEberhardt opened this issue Aug 23, 2024 · 2 comments
Open
Tracked by #47

Create a standard structure for Threats and Controls #26

ColinEberhardt opened this issue Aug 23, 2024 · 2 comments
Labels
📚 governance-framework ❓ question Further information is requested

Comments

@ColinEberhardt
Copy link
Collaborator

We need to decide on a standard structure for how we document Threats and Controls, i.e. what information we include in each case, and what metadata to include. Currently we have:

  • Threat
    • Identifier - sequential, numeric, prefixed
    • type - a threat classification using the CIA triad
    • title - brief, few words
    • narrative - a free-form text narrative, containing a Severity section
  • Control
    • identifier - sequential, numeric, prefixed
    • type - Preventative or Detective
    • mitigates - the list of threats a give control mitigates
    • title - brief, few words
    • narrative - a free-form text narrative, containing a Potential Tools and Approaches section
@ColinEberhardt ColinEberhardt added ❓ question Further information is requested 📚 governance-framework labels Aug 23, 2024
@ColinEberhardt
Copy link
Collaborator Author

Personally I think the current metadata is sufficient. However, I don't think the classification of Threat / Control is entirely compatible with what we are capturing. I'd prefer Risk / Mitigation as I feel this is a better fit.

@Neetuj
Copy link

Neetuj commented Sep 4, 2024

I agree that instead of Threats is makes more sense to be called as Risks ( Product /consumer of the Threatmodel can decide how to act on the risk and accept, mitigate or pivot).
Severity could be broken down in Likelihood + impact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📚 governance-framework ❓ question Further information is requested
Projects
Status: In Progress
Development

No branches or pull requests

2 participants