The ATT&CK Navigator is designed to provide basic navigation and annotation of ATT&CK matrices, something that people are already doing today in tools like Excel. We've designed it to be simple and generic - you can use the Navigator to visualize your defensive coverage, your red/blue team planning, the frequency of detected techniques or anything else you want to do. The Navigator doesn't care - it just allows you to manipulate the cells in the matrix (color coding, adding a comment, assigning a numerical value, etc.). We thought having a simple tool that everyone could use to visualize the matrix would help make it easy to use ATT&CK.

The principal feature of the Navigator is the ability for users to define layers - custom views of the ATT&CK knowledge base - e.g. showing just those techniques for a particular platform or highlighting techniques a specific adversary has been known to use. Layers can be created interactively within the Navigator or generated programmatically and then visualized via the Navigator.

There is an Install and Run section below that explains how to get the ATT&CK Navigator up and running. You can also try the Navigator out by pointing your browser here. The default is the Enterprise ATT&CK domain, but the Mobile ATT&CK domain can be utilized here. See Enterprise and Mobile Domains below for information on how to set up the ATT&CK Navigator on local instances to use the two different domains.

Important Note: Layer files uploaded when visiting our Navigator instance hosted on GitHub Pages are NOT being stored on the server side, as the Navigator is a client-side only application. However, we still recommend installing and running your own instance of the ATT&CK Navigator if your layer files contain any sensitive content.

Use our GitHub Issue Tracker to let us know of any bugs or others issues that you encounter. We also encourage pull requests if you've extended the Navigator in a cool way and want to share back to the community!

See CONTRIBUTING.md for more information on making contributions to the ATT&CK Navigator.

• Node.js version 8 or greater
• AngularCLI

• Chrome
• Firefox
• Internet Explorer
• Safari¹
• Edge
• Opera

¹ There is a recorded issue with using the ATT&CK Navigator on Safari. If the user reloads the page but cancels the action when prompted, the refresh icon in the browser window remains in the cancel reload state. This is believed to be an issue with Safari and not with the application.

1. Navigate to the nav-app directory
2. Run npm install

1. Run ng serve within the nav-app directory
2. Navigate to localhost:4200 in browser

1. Run ng build within the nav-app directory
2. Copy files from nav-app/dist/ directory

1. Install the Navigator as per instructions above.
2. Follow instructions under loading content from local files to configure the Navigator to populate the matrix without an internet connection. For enterprise-attack, use this file. For mobile-attack, use this file. For pre-attack, use this file.

When viewing the app in a browser, click on the ? icon to the right of the ATT&CK^™ Navigator title to view its documentation.

By default, the ATT&CK Navigator will generate a matrix view of the tactics and techniques matrix for the Enterprise ATT&CK technology domain knowledge base. All tactics and techniques in this domain are contained within the act stage, which is also pre-selected by default.

To instead generate a matrix view of the Mobile ATT&CK technology domain knowledge base, change the domain value in nav-app/src/assets/config.json to mitre-mobile. Use Device Access and Network-Based Effects tactics and techniques in this domain are contained within the act stage, which is pre-selected by default. Obtain Device Access tactics and techniques are contained within the prepare stage, which can be manually selected.

PRE-ATT&CK is included in the matrix view for either domain if the prepare stage is manually selected within the layer control filters.

The tactics displayed in the ATT&CK matrices are pulled from the file nav-app/src/assets/tacticsData.json where they are organized by domain. We will keep this file up to date as tactics are added and edited in new releases of ATT&CK.

The layers folder currently contains a Python script that automatically generates layer files. We will continue to add content to this repository as new scripts are implemented. Also, feel free to create pull requests if you want to add new capabilities here!

The layers folder's README contains more detailed information about how to utilize this set of scripts, and LAYERFORMATv2_1.md describes version 2.1 of the layer file format for the Navigator.

More information on how layers are used and developed can be found in the ATT&CK Navigator documentation that can be viewed by clicking ? when running the app in a browser.

To create custom options to the ATT&CK^™ Navigator context menu using data in the Navigator, objects must be added to the array labeled custom_context_menu_options in nav-app/src/assets/config.json. Each object must have a property label, which is the text displayed in the context menu, and a property url, which is where the user is navigated.

To utilize data on right-clicked technique in the url, parameters surrounded by tildes can be added to the string. For example: using http://www.someurl.com/~Technique_ID~ as the url in the custom option would lead to http://www.someurl.com/T1098, if the right-clicked technique's ID was T1098.

Available technique data able to be added to the url:

• Technique_ID returns the Technique ID
• Technique_Name returns the Technique Name with the first letter of each word capitalized and using underscores between words
• Tactic_Name returns the Tactic Name with the first letter of each word capitalized and using underscores between words

Example custom context menu object:

{
    "label": "custom technique url",
    "url": "https://attack.mitre.org/techniques/~Technique_ID~"
}

By default, the Navigator loads content from the MITRE CTI TAXII server at https://cti-taxii.mitre.org.

1. Edit the config.json file in the nav-app/src/assets directory
2. Set the enabled property in taxii_server to true
3. Set the url property in taxii_server to your server's URL
4. Set the values of the collections dictionary to the collection UUIDs your TAXII server has set

It's possible to populate the the Navigator using files that consist of bundles of STIX objects, similarly to this file.

1. Put the stix bundles in src/assets. This will tell the server hosting the Navigator to host the data as well.
2. Configure the navigator to use these files. In src/assets/config.json:
   1. Change enterprise_attack_url to the path to the enterprise-attack bundle (e.g assets/enterprise-attack.json).
   2. Change mobile_attack_url to the path to the mobile-attack bundle (e.g assets/mobile-attack.json).
   3. Change pre_attack_url to the path to the pre-attack bundle (e.g assets/pre-attack.json).
   4. Change taxii_server.enabled to false.

1. Navigate to the nav-app directory
2. Run docker build -t yourcustomname .
3. Run docker run -p 4200:4200 yourcustomname
4. Navigate to localhost:4200 in browser

The Navigator can be configured so as to load a set of layers upon initialization. These layers can be from the web and/or from local files. Local files to load should be placed in the nav-app/src/assets/ directory.

1. Set the enabled property in default_layers in src/assets/config.json to true
2. Add the paths to your desired default layers to the urls array in default_layers. For example,

   "default_layers": {
        "enabled": true,
        "urls": [
            "assets/example.json", 
            "https://raw.githubusercontent.com/mitre-attack/attack-navigator/master/layers/data/samples/Bear_APT.json"
        ]
    }

   would load example.json from the local assets directory, and Bear_APT.json from this repo's sample layer folder on Github.
3. Load/reload the Navigator

A single default layer from the web can also be set using a query string in the Navigator URL. Refer to the in-application help page section "Customizing the Navigator" for more details.

The features array in nav-app/src/assets/config.json lists Navigator features you may want to disable. Setting the enabled field on a feature in the configuration file will hide all control elements related to that feature.

However, if a layer is uploaded with an annotation or configuration relating to that feature it will not be hidden. For example, if comments are disabled the ability to add a new comment annotation will be removed, however if a layer is uploaded with comments present they will still be displayed in tooltips and and marked with an underline.

Features can also be disabled using the create customized Navigator feature. Refer to the in-application help page section "Customizing the Navigator" for more details.

If you want to embed the Navigator in a webpage, use an iframe:

<iframe src="https://mitre-attack.github.io/attack-navigator/enterprise/" width="1000" height="500"></iframe>

If you want to imbed a version of the Navigator with specific features removed (e.g tabs, adding annotations), or with a default layer, we recommend using the create customized Navigator feature. Refer to the in-application help page section "Customizing the Navigator" for more details.

The following is an example iframe which embeds our *Bear APTs layer with tabs and the ability to add annotations removed:

<iframe src="https://mitre-attack.github.io/attack-navigator/enterprise/#layerURL=https%3A%2F%2Fraw.githubusercontent.com%2Fmitre%2Fattack-navigator%2Fmaster%2Flayers%2Fdata%2Fsamples%2FBear_APT.json&tabs=false&selecting_techniques=false" width="1000" height="500"></iframe>

Cyber Threat Intelligence repository of the ATT&CK catalog expressed in STIX 2.0 JSON.

ATT&CK™ is a curated knowledge base and model for cyber adversary behavior, reflecting the various phases of an adversary’s lifecycle and the platforms they are known to target. ATT&CK is useful for understanding security risk against known adversary behavior, for planning security improvements, and verifying defenses work as expected.

https://attack.mitre.org

Structured Threat Information Expression (STIX™) is a language and serialization format used to exchange cyber threat intelligence (CTI).

STIX enables organizations to share CTI with one another in a consistent and machine readable manner, allowing security communities to better understand what computer-based attacks they are most likely to see and to anticipate and/or respond to those attacks faster and more effectively.

STIX is designed to improve many different capabilities, such as collaborative threat analysis, automated threat exchange, automated detection and response, and more.

https://oasis-open.github.io/cti-documentation/

Copyright 2018 The MITRE Corporation

Approved for Public Release; Distribution Unlimited. Case Number 18-0128.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

This project makes use of ATT&CK^™

ATT&CK Terms of Use