{"version":"2.1.23","anchor":"updated-security-policy-for-code-analysis","canonical_anchor":"updated-security-policy-for-code-analysis","heading":"Updated Security Policy for Code Analysis","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.23\/e\/updated-security-policy-for-code-analysis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.23","markdown":"### Updated Security Policy for Code Analysis\n\nThe system prompt for security-related tasks has been expanded to better support legitimate security work:\n\n**Previous policy**: \"Assist with defensive security tasks only\"\n\n**New policy**: \"Assist with authorized security testing, defensive security, CTF challenges, and educational contexts\"\n\n**Details**\n\n- Now explicitly allows: pentesting engagements, CTF competitions, security research, defensive use cases\n- Still refuses: destructive techniques, DoS attacks, mass targeting, supply chain compromise, detection evasion for malicious purposes\n- Dual-use security tools (C2 frameworks, credential testing, exploit development) require clear authorization context\n\n**Evidence**\n\nPolicy string at line 550045 (contains `\"authorized security testing\"`, `\"CTF challenges\"`)"}