In this article
- Update the MTMT default mapping file.
- Create a Trust Zone (see https://support.iriusrisk.com/hc/en-us/articles/6093686846609-How-to-create-a-trust-zone)
- Import a .tm7 file using Postman
To create a project:
To update a project
For this guide , we will use the following DFD as an example:
1. Establish the boundaries being used in the DFD by the display name and the stencil name:
1.1 Border Boundary: Cloud Service uses the Stencil Generic Trust Border Boundary:
1.2 Border Boundary: Internet uses the Stencil Generic Trust Border Boundary
1.3 Border Boundary: Public Cloud uses the Stencil Azure Trust Boundary
2. Download the default mapping file for MTMT (mtmt_default_mapping_example.yaml) from Github
3. Note the attributes using for mapping the trust zones:
-label : This is the Stencil name
-type: For Importing via OTM, this attribute is ignored., however, we recommend entering the display name instead
-id: This is the Unique ID of the TZ in IR
4. Under the trustzones section, identify if the list meets the needs of your DFD.
4.1 Note the following:
4.1.1 In this example, the default mapping file contains a label for Generic Trust Border Boundary which will map that boundary to the Public TZ within IR since the id in the mapping file is the same as the
- label: Generic Trust Border Boundary
4.1.2 Since our DFD contains two boundaries with the same label (Generic Trust Border Boundary ), and one is nested in the other.
4.1.3 The default mapping file does not contain a mapping for Azure Trust Boundary.
4.2 Make the following assumptions:
4.2.1 Map the Cloud Service boundary border to the Public TZ
4.2.2 Map the Internet boundary border to the Internet TZ
4.2.3 For border boundary Public Cloud [1.3], we will need to create a new TZ since the rating has been evaluated to be 50 and the for Public Cloud TZ is too high (at 60).
5. Create a new TZ and note the Unique ID:
Trust Rating: 50