From bf0731c08028876d5fa9af21e7ed84cd997d2e9f Mon Sep 17 00:00:00 2001
From: Adam Mashinchi <78813159+amashinchi-rc@users.noreply.github.com>
Date: Thu, 3 Jun 2021 13:51:20 -0700
Subject: [PATCH] Updating spec for ATT&CKv9

Including changes noted in https://github.com/redcanaryco/atomic-red-team/issues/1491
---
 atomic_red_team/spec.yaml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/atomic_red_team/spec.yaml b/atomic_red_team/spec.yaml
index 0f46a9c4..9ccd2b42 100644
--- a/atomic_red_team/spec.yaml
+++ b/atomic_red_team/spec.yaml
@@ -51,6 +51,15 @@ atomic_tests:
   # - windows
   # - macos
   # - linux
+  # - office-365
+  # - azure-ad
+  # - google-workspace
+  # - saas
+  # - iaas
+  # - containers
+  # - iaas:gcp
+  # - iaas:azure
+  # - iaas:aws
   supported_platforms:
     - windows
 
@@ -106,6 +115,7 @@ atomic_tests:
   # a list of executors that can execute the attack commands of this atomic test. There are almost always going to be one of these
   # per test, but there are cases where you may have multiple - for example, separate executors for `sh`
   # and `bash` when working on linux OSes.
+  # Names of cloud/container specific runtimes can also be used, such as `aws`, `az`, and `gcloud`.
   executors:
   # the name of the executor describes the framework or application in which the test should be executed.
   #