Fix: #165. Typo in SAMM V-ST-A.

Author: ioggstream

src/assets/YAML/default/Implementation/DevelopmentAndSourceControl.yaml

@@ -17,7 +17,7 @@ Implementation:
       - $ref: src/assets/YAML/default/implementations.yaml#/implementations/sonarqube
       references:
         samm2:
-        - V-ST-A-1-1
+        - V-ST-1-A
         iso27001-2017: []
       isImplemented: false
       evidence: ""
@@ -38,7 +38,7 @@ Implementation:
       - $ref: src/assets/YAML/default/implementations.yaml#/implementations/pre-commit-synopsis
       references:
         samm2:
-        - V-ST-A-1-1
+        - V-ST-1-A
         iso27001-2017: []
       isImplemented: false
       evidence: ""

src/assets/YAML/default/TestAndVerification/StaticDepthForApplications.yaml

@@ -40,7 +40,7 @@ Test and Verification:
       - $ref: src/assets/YAML/default/implementations.yaml#/implementations/appscan-vscode-extension
       references:
         samm2:
-        - V-ST-A-1-1
+        - V-ST-1-A
         iso27001-2017:
         - hardening is not explicitly covered by ISO 27001 - too specific
         - 13.1.3

src/assets/YAML/generated/generated.yaml

@@ -1754,7 +1754,7 @@ Implementation:
         - linting
       references:
         samm2:
-        - V-ST-A-1-1
+        - V-ST-1-A
         iso27001-2017: []
       isImplemented: false
       evidence: ""
@@ -1782,7 +1782,7 @@ Implementation:
         - pre-commit
       references:
         samm2:
-        - V-ST-A-1-1
+        - V-ST-1-A
         iso27001-2017: []
       isImplemented: false
       evidence: ""
@@ -3871,7 +3871,7 @@ Test and Verification:
         - sast
       references:
         samm2:
-        - V-ST-A-1-1
+        - V-ST-1-A
         iso27001-2017:
         - hardening is not explicitly covered by ISO 27001 - too specific
         - 13.1.3