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 "Layer Upgrade" UI #181

Closed
isaisabel opened this issue Jun 23, 2020 · 0 comments
Closed

Add "Layer Upgrade" UI #181

isaisabel opened this issue Jun 23, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request Points: 15 15 agile story points priority/high High priority Issue seeking feedback Seeking feedback from the community on this issue timescale/imminent Ready to be assigned to developers
Milestone

Comments

@isaisabel
Copy link
Contributor

isaisabel commented Jun 23, 2020

As a user of ATT&CK, I want to be able to upgrade layers created in older versions of ATT&CK with an intuitive UI.

  • This UI should perform the same operations as the update-layers script automatically, and provide notification to the users of the revocations that were followed.
  • The UI should notify the user of what objects have changed between the two versions (see also diff_stix.py for other implementations showing changes between STIX bundles).
    • It should highlight changes in two lists, one for objects which have changed which had annotations, and one for objects which changed which did not have annotations. These lists should be shown as adjacent columns or tabs.
    • Changes should be grouped by type:
      • Changes which removed the object (deletion or revocation) and have therefore removed annotations the user had added.
      • Changes to the object content (major and minor changes), which may require updated annotations
      • Object additions, which may require new annotations
      • which objects have been upgraded automatically
    • Possibly allow the user to filter the lists to show only techniques, or all objects (which would be useful if the user was tracking mitigations or APT coverage)

This UI should take the form of a sidebar adjacent to the Matrix. Clicking on a change or section should select the object/objects within the section where they occur in the matrix, and likewise hovering should highlight objects where they occur in the matrix. Highlights and selections should also work the other direction (where they occur in the matrix they also occur in the sidebar).

For objects which changed that have annotations (in particular cases where the object is no longer in the matrix, e.g revocations and deletions), the previous annotations should be shown on the item so that the user can remap them.

The user should be able to minimize and expand the sidebar if they so choose.

@isaisabel isaisabel added enhancement New feature or request priority/high High priority Issue seeking feedback Seeking feedback from the community on this issue timescale/short-term Becomes timescale/imminent in weeks or months labels Jun 23, 2020
@isaisabel isaisabel modified the milestones: Version 4.1, Version 4.2 Oct 23, 2020
@isaisabel isaisabel added timescale/imminent Ready to be assigned to developers and removed timescale/short-term Becomes timescale/imminent in weeks or months labels Feb 16, 2021
@isaisabel isaisabel modified the milestones: Version 4.3, Version 4.4 Mar 19, 2021
@clemiller clemiller self-assigned this Apr 20, 2021
clemiller added a commit that referenced this issue May 17, 2021
clemiller added a commit that referenced this issue May 17, 2021
iguannalin added a commit that referenced this issue May 19, 2021
iguannalin added a commit that referenced this issue May 19, 2021
@isaisabel isaisabel added the Points: 15 15 agile story points label Jun 24, 2021
isaisabel added a commit that referenced this issue Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Points: 15 15 agile story points priority/high High priority Issue seeking feedback Seeking feedback from the community on this issue timescale/imminent Ready to be assigned to developers
Projects
None yet
Development

No branches or pull requests

2 participants