php-symfony-audit

To audit Symfony security.yaml configurations, this Skill statically analyzes access control rules and maps identified risks to standardized vulnerability taxonomies like AUTH and CFG. It produces actionable findings with clear evidence references and remediation guidance.

Twig template escaping affects XSS risks by either neutralizing or exposing malicious payloads depending on automatic escaping or raw output usage. The audit identifies unsafe Twig output expressions and maps them to standardized XSS vulnerability categories.

Yes, you can detect CSRF protection gaps in a Symfony project using static analysis. This Skill examines CSRF token configurations and behaviors, mapping any identified weaknesses to the CSRF vulnerability taxonomy with actionable remediation steps.

The best way to map expression language vulnerabilities is to statically analyze Symfony expressions and access control configurations. This process identifies logical flaws and maps them to unified vulnerability types like LOGIC and TPL for cross-project comparison.

Yes, this Symfony security audit requires specific framework artifacts to run effectively. The analysis ensures the presence of Symfony project indicators and validates specific framework configurations like security.yaml before producing the risk mapping report.

Limitations exist when auditing Symfony access control with static analysis if specific framework artifacts or project indicators are missing. The audit requires valid Symfony configurations to map vulnerabilities accurately and cannot analyze non-Symfony code structures.