feat: Add next_steps field to finding's list of attributes (#476)

PiperOrigin-RevId: 440383959
Source-Link: googleapis/googleapis@6a276f6
Source-Link: https://github.com/googleapis/googleapis-gen/commit/f94fc64061837033bab88c65075e1814edb6133a
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZjk0ZmM2NDA2MTgzNzAzM2JhYjg4YzY1MDc1ZTE4MTRlZGI2MTMzYSJ9
See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

protos/google/cloud/securitycenter/v1/finding.proto

@@ -272,4 +272,7 @@ message Finding {
 
   // Represents IAM bindings associated with the Finding.
   repeated IamBinding iam_bindings = 39;
+
+  // Next steps associate to the finding.
+  string next_steps = 40;
 }

protos/google/cloud/securitycenter/v1/mitre_attack.proto

@@ -78,7 +78,7 @@ message MitreAttack {
 
   // MITRE ATT&CK techniques that can be referenced by SCC findings.
   // See: https://attack.mitre.org/techniques/enterprise/
-  // Next ID: 30
+  // Next ID: 31
   enum Technique {
     // Unspecified value.
     TECHNIQUE_UNSPECIFIED = 0;
@@ -169,6 +169,9 @@ message MitreAttack {
 
     // T1485
     DATA_DESTRUCTION = 29;
+
+    // T1484
+    DOMAIN_POLICY_MODIFICATION = 30;
   }
 
   // The MITRE ATT&CK tactic most closely represented by this finding, if any.