GitHub has added a self‑serve option for Team‑level organizations to start a trial of GitHub Advanced Security, which bundles Code Security scanning and Secret Protection. Engineers responsible for AI pipelines, cloud platforms, CI/CD, or security can now evaluate these capabilities without upgrading their plan first.
How to enable the trial
- Navigate to the organization’s Overview page and select the trial prompt.
- Open the Billing and licensing section, then choose the Licensing page to start the trial.
- Complete a Risk Assessment; the final page offers a trial activation button.
What the trial includes
The trial surface‑levels two core services:
- GitHub Code Security: automated analysis that flags vulnerable code patterns during pull‑request review.
- GitHub Secret Protection: scanning for exposed credentials or tokens in repository history and new commits.
Operational considerations
Enabling the trial injects additional scanning steps into existing CI pipelines, which may increase run times or generate new alerts. Because the trial is self‑served, there is no immediate change to the organization’s billing, but practitioners should track the trial’s end point to avoid unexpected licensing shifts. Integration points remain the same – the services hook into the same repository events used by standard GitHub workflows, so no new configuration files are required beyond the default settings.
Related CloudNinjas coverage: security.
What This Means For Practitioners
Use the trial to benchmark false‑positive rates and performance impact in your current pipelines. Document any policy changes needed to act on findings, and plan a migration path if the trial proves valuable. Keep an eye on the trial’s expiration and be ready to either adopt the full Advanced Security license or disable the features to maintain a predictable cost model.