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

Filter options on the beta sub-technique version have duplicates #164

Closed
olafhartong opened this issue May 12, 2020 · 3 comments
Closed
Assignees
Labels
bug Something isn't working timescale/imminent Ready to be assigned to developers

Comments

@olafhartong
Copy link

The filtering for threat groups has a lot of duplicate entries, some examples being;
APT16
APT17
APT28

Additionally it seems the tagging of the techniques also has some issues, for instance in the current navigator APT1 has better coverage than in the beta edition.

Both might be caused by a similar parsing flaw, or completely separate ;)

@isaisabel isaisabel added bug Something isn't working timescale/imminent Ready to be assigned to developers labels May 13, 2020
@isaisabel
Copy link
Contributor

Hi @olafhartong,

It looks like some of the duplicated APTs are objects found in multiple domains (e.g APT28 and APT1 are both duplicated, and they're both in PRE-ATT&CK and Enterprise). I'm not yet sure what's causing the issue with APT17 and APT16 since they're single-domain.

With regards to the coverage difference (12 associated techniques vs 22 before), that's more of a matter of how we executed the sub-techniques refactor, and not really a Navigator issue. I'd recommend reaching out to the ATT&CK team (contact page here) if you have questions or concerns about the coverage difference.

@isaisabel
Copy link
Contributor

isaisabel commented May 13, 2020

Actually, looking at the beta version of APT1, it looks like there should be 20 associated techniques (the number in the techniques used table), not 12 as selected in the multiselect interface. So you're right that there may be a bug involved there.

@isaisabel
Copy link
Contributor

@olafhartong we've fixed this bug and merged it into the feature/subtechniques-3.1 branch. It'll be moved to develop once we're done with the rest of the features in the v3.1 milestone.

I'm closing the issue so that we can track our progress in the milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working timescale/imminent Ready to be assigned to developers
Projects
None yet
Development

No branches or pull requests

3 participants