<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github-Advanced-Security on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/github-advanced-security/</link><description>Recent content in Github-Advanced-Security on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 16 Sep 2026 15:13:50 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/github-advanced-security/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Enterprise can now enforce Advanced Security configurations org-wide</title><link>https://curadevops.metacog.co.kr/insights/2026-09-16-enforce-github-advanced-security-configurations/</link><pubDate>Wed, 16 Sep 2026 15:13:50 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-16-enforce-github-advanced-security-configurations/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> GHAS enforcement is a GitHub admin feature, not a pipeline change, but CI/CD engineers should understand that enterprise-level security configurations may now be locked — worth noting if code-scanning settings are managed in repo workflows.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This new enforcement capability lets enterprise admins lock GHAS settings so org/repo owners can&amp;rsquo;t override them — evaluate adopting enterprise-wide enforcement to standardize code-scanning and security policies across all organizations this quarter.&lt;/li>
&lt;/ul></description></item></channel></rss>