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 TLP note to EM implementation notes #113

Merged
merged 2 commits into from
Apr 26, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/howto/process_implementation.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,17 @@ Our experience at the CERT/CC shows that this distinction is rarely a significan
simply publish at their own pace shortly after the embargo ends.
However, at times, case Participants may find it necessary to coordinate even more closely on publication scheduling.

!!! example "TLP and Embargoes"

The [Traffic Light Protocol (TLP)](https://www.first.org/tlp){:target="_blank"} is a useful tool for managing the
dissemination of sensitive information.
TLP can be used to indicate how widely information can be shared and what restrictions apply during an embargo.
For example, an embargoed case might be marked <span style="color:#FFC000;background-color:#000000">**TLP:AMBER**</span>
to indicate that the information is sensitive and should be shared only with those who need to know.
Thus, an embargo declaration might take the form of "This case is <span style="color:#FFC000;background-color:#000000">**TLP:AMBER**</span>
until 2024-03-31 23:59:59 UTC, at which time it becomes <span style="color:#FFFFFF;background-color:#000000">**TLP:CLEAR**</span>."
We have more to say about the use of TLP in CVD in the [CERT Guide to CVD](https://certcc.github.io/CERT-Guide-to-CVD/howto/operation/opsec/){:target="_blank"}.

## CS Implementation Notes

Because part of the CS model is Participant specific and the other is global to the case, we address each part below.
Expand Down
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,7 @@ nav:
- Build a Behavior Tree library: 'adr/0003-build-custom-python-bt-engine.md'
- Use Factory Pattern for BT nodes: 'adr/0004-use-factory-methods-for-common-bt-node-types.md'
- Use ActivityStreams Vocabulary as Message Format: 'adr/0005-activitystreams-vocabulary-as-vultron-message-format.md'
- Use CalVer for Versioning: 'adr/0006-use-calver-for-project-versioning.md'
- About:
- Contributing: 'about/contributing.md'
- FAQ: 'about/faq.md'
Expand Down