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

Incident/Event #1

Open
6 tasks
johnwunder opened this issue Feb 6, 2017 · 1 comment
Open
6 tasks

Incident/Event #1

johnwunder opened this issue Feb 6, 2017 · 1 comment

Comments

@johnwunder
Copy link

johnwunder commented Feb 6, 2017

The development of one or more SDOs to capture incident and event information.

Work area: Working Concepts

Scope

The capture of information related to internal security events, internal security incidents, and external security-relevant events.

Examples

  • A malware infection on an internal laptop
  • Tracking an incident response to an APT intrusion
  • A threat actor changes a C2 domain
  • Reporting an incident to a third-party, such as US-CERT or DC3
  • Public incident repositories, such as VERIS

Open Questions

  • Is there a single SDO to capture both incident and event information?
  • If so, how is the status "incident" captured?
  • Do you need to distinguish between internal, security-relevant events and external information?
  • How do you track workflow/timestamps?
  • How do you track POCs?
  • How is it related to observed data?
@skelley1
Copy link

skelley1 commented Mar 7, 2018

This has been pushed from the 2.1 since we did not agree on a proposal.

@jordan2175 jordan2175 modified the milestones: 2.2-csd01-wd01, unknown Jul 2, 2019
@jordan2175 jordan2175 removed this from the unknown milestone Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants