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

Add event.tlp #792

Closed
weichea opened this issue Mar 18, 2020 · 7 comments
Closed

Add event.tlp #792

weichea opened this issue Mar 18, 2020 · 7 comments
Labels

Comments

@weichea
Copy link

weichea commented Mar 18, 2020

I couldn't find any field for event traffic light protocol (TLP). Is there any existing field for tlp if no, could we add them?

@webmat
Copy link
Contributor

webmat commented Mar 26, 2020

Can you expand on this?

@weichea
Copy link
Author

weichea commented Mar 28, 2020

Hi @webmat

TLP defines the sensitivity of information/event. So could we have add event.tlp that describe sensitivity of an event.

https://www.us-cert.gov/tlp

@ebeahan
Copy link
Member

ebeahan commented Jul 13, 2020

@weichea Can you provide any additional context or examples of the use cases you hand in mind for capturing TLP fields?

@ebeahan
Copy link
Member

ebeahan commented Jul 20, 2020

ping @shimonmodi - any thoughts on this from a threat intel perspective?

@shimonmodi
Copy link
Contributor

@ebeahan - first of all, apologies for not responding sooner. my notification settings were off and didn't see this. thanks @jamiehynds.

TLP is primarily used in incident/intelligence sharing and dissemination by industry specific sharing groups & government agencies. Essentially it dictates a contract between the sender and receiver - each of the 4 level of TLP dictate what privileges the receiver has with respect to the information being shared. Implicitly it also conveys level of sensitivity and criticality about the information being shared.

With our existing capabilities I can see users:

  1. wanting to know if they have received TLP:RED information, meaning its high severity and criticality and should be taken into consideration right away. this could flow into our rules, where users filter on alerts generated by TLP:RED information.
  2. wanting to know if any events from ingestion sources correlate with TLP marked information received from partners/peers.

Currently we don't support an incident/intel sharing workflow (for e.g. - company x, which belongs to financial services, has just detected a phishing attack and now wants to share their incident analysis with other financial services companies) but at some point I envision us doing so.

We need to represent TLP, along with a number of other threat intelligence related fields in ECS. Just not sure if event is the right parent field for it. need to think through it.

@ebeahan
Copy link
Member

ebeahan commented Aug 3, 2020

No worries and thanks for your insights @shimonmodi! 😄

@webmat
Copy link
Contributor

webmat commented Nov 5, 2020

@shimonmodi Seeing discussion about TLP over in #1037, I think we can close this one, right?

@ebeahan ebeahan closed this as completed Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants