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.

Sign up for GitHub

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

Jump to bottom

Remove bi-directional relationship between Threat Actor and Campaign #192

Open
johnwunder opened this issue Aug 6, 2014 · 0 comments
Open

Remove bi-directional relationship between Threat Actor and Campaign #192

johnwunder opened this issue Aug 6, 2014 · 0 comments
Labels
2.0-Prototyped 2.0-Yes Breaks Backwards Compatibility Data-Model-centric Effort-hours Enhancement Relationship-related Requires Community Feedback Requires Investigation Simplification Tier2

Comments

@johnwunder
Copy link
Member

STIX allows Threat Actors to be related to Campaigns and Campaigns can be related to Threat Actors. Most other relationships in STIX are uni-directional.

Consider the use cases behind each direction and potentially deprecate one direction or the other.

Related and potentially overcome by #70.
@gtback gtback changed the title Consider usage of Threat Actor <=> Campaign bi-directional relationship Modify bi-directional relationship between Threat Actor and Campaign Nov 3, 2014
@johnwunder johnwunder changed the title Modify bi-directional relationship between Threat Actor and Campaign Remove bi-directional relationship between Threat Actor and Campaign Nov 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2.0-Prototyped 2.0-Yes Breaks Backwards Compatibility Data-Model-centric Effort-hours Enhancement Relationship-related Requires Community Feedback Requires Investigation Simplification Tier2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@johnwunder @ikiril01 @sbarnum