Start a GHAS Trial' from the Security Risk Assessments [GA] (#61280)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Laura Coursen <lecoursen@github.com>

Author: 3 people

content/code-security/tutorials/secret-protection-adoption-path.md

@@ -40,6 +40,7 @@ journeyTracks:
       - href: '/code-security/reference/secret-security/supported-secret-scanning-patterns'
       - href: '/code-security/how-tos/secure-at-scale/configure-organization-security/configure-specific-tools/estimating-the-price-of-secret-protection'
       - href: '/code-security/tutorials/remediate-leaked-secrets/calculating-the-cost-savings-of-push-protection'
+      - href: '/code-security/tutorials/trialing-github-advanced-security/trial-advanced-security'
   - id: 'pilot'
     title: 'Phase 3: Pilot GitHub Secret Protection'
     description: 'Run a pilot to validate GHSP with a small set of repositories before organization-wide enablement. Select 5-10 repositories with active development and known secret exposure. If you estimated pricing in Phase 2, you''ll confirm costs as part of the enablement flow. A successful pilot demonstrates security value quickly, identifies workflow adjustments, and gathers feedback to refine your rollout strategy.'

content/code-security/tutorials/secure-your-organization/interpreting-code-security-risk-assessment-results.md

@@ -82,9 +82,9 @@ Also look for the following indicators, which may require broader intervention b
 * **Many repositories affected by the same rule**: Suggests a systemic pattern that may require team training or updated coding standards
 * **High vulnerability counts in a specific language**: May point to framework-level issues or missing scanning tooling for that language
 
-## Next steps
+{% data reusables.security.start-ghas-trial %}
 
 To start remediating vulnerabilities with {% data variables.copilot.copilot_autofix_short %}, enable {% data variables.product.prodname_GH_code_security_always %} for your organization. You have two options:
 
 * To enable {% data variables.product.prodname_GH_code_security_always %} for an individual repository, click **Enable** next to a repository in the "Repositories scanned" table.
-* To enable {% data variables.product.prodname_GH_code_security_always %} across your organization, click **Enable {% data variables.product.UI_code_security_scanning %}** at the top of the page. Here, you can choose whether to enable it for all repositories or selected repositories, then review the estimated cost before confirming.
+* To enable {% data variables.product.prodname_GH_code_security_always %} across your organization, click **Enable {% data variables.product.UI_code_security_scanning %}** at the top of the page. Here, you can choose whether to enable it for all repositories or selected repositories, then review the estimated cost before confirming.

content/code-security/tutorials/secure-your-organization/interpreting-secret-risk-assessment-results.md

@@ -91,6 +91,4 @@ Finally, look for the following indicators, which may require additional prevent
 * **Repeated secret types**: Suggests specific workflows or teams need targeted intervention
 * **Common secret categories**: May point to particular CI/CD processes requiring security improvements
 
-## Next steps
-
-After understanding your secret exposure, select repositories for a {% data variables.product.prodname_GH_secret_protection %} pilot. See [AUTOTITLE](/code-security/concepts/security-at-scale/best-practices-for-selecting-pilot-repositories).
+{% data reusables.security.start-ghas-trial %}

data/reusables/security/start-ghas-trial.md

@@ -0,0 +1 @@
+Remediating the vulnerabilities or leaks identified by the risk assessment is easier with  {% data variables.product.prodname_GHAS %}. Eligible enterprise administrators can start a trial for their entire enterprise straight from the results page.