Fixed visualization bug

Author: sethsec

data/paths/codedeploy/codedeploy-001.yaml

@@ -184,7 +184,7 @@ attackVisualization:
       color: '#ffeb99'
       description: The pre-attached instance profile role has elevated but non-admin permissions. The lifecycle hook script can leverage those credentials for data access, resource modification, or further escalation depending on what the role can do.
 
-    - id: no
+    - id: no_access
       label: No additional access
       type: outcome
       color: '#cccccc'
@@ -262,7 +262,7 @@ attackVisualization:
       description: If the pre-attached instance profile role has elevated but non-admin permissions, the lifecycle hook script can leverage those credentials for data access or further escalation paths.
 
     - from: admin_role
-      to: no
+      to: no_access
       label: If instance profile role has minimal permissions
       branch: C
       condition: no_permissions

data/paths/cognitoidentity/cognitoidentity-001.yaml

@@ -179,7 +179,7 @@ attackVisualization:
       color: '#ffeb99'
       description: The bound role has elevated but non-admin permissions. Any internet caller can obtain credentials scoped to those permissions. Useful for data access (S3, RDS, DynamoDB) or as a stepping stone for additional privilege escalation paths.
 
-    - id: no
+    - id: no_access
       label: No additional access
       type: outcome
       color: '#cccccc'
@@ -269,7 +269,7 @@ attackVisualization:
       description: If the bound role has elevated but non-admin permissions, the vended credentials enable data access or lateral movement. Further escalation may be possible depending on what the role can do.
 
     - from: admin_role
-      to: no
+      to: no_access
       label: If role has minimal permissions
       branch: C
       condition: no_permissions

data/paths/scheduler/scheduler-001.yaml

@@ -137,7 +137,7 @@ attackVisualization:
       color: '#ffeb99'
       description: The passed role has elevated but non-admin permissions. The schedule can invoke AWS SDK actions within those permissions. The attacker may be able to access data, modify resources, or find further escalation paths depending on what the role can do.
 
-    - id: no
+    - id: no_access
       label: No additional access
       type: outcome
       color: '#cccccc'
@@ -187,7 +187,7 @@ attackVisualization:
       description: If the passed role has elevated but non-admin permissions, the schedule can invoke AWS SDK actions within those permissions. The attacker can target different SDK APIs via the universal target to leverage whatever the role can do.
 
     - from: admin_role
-      to: no
+      to: no_access
       label: If role has minimal permissions
       branch: C
       condition: no_permissions