{"version":"2.1.232","anchor":"new-third-party-attack-risk-category","canonical_anchor":"new-third-party-attack-risk-category","heading":"New third-party attack risk category","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/new-third-party-attack-risk-category","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### New third-party attack risk category\n\nDeny rules can now be labelled as third-party attack risk alongside existing categories.\n\n**What**\n\nA `third_party_attack` identifier joins the risk categories used when rendering deny rules from settings, sitting between the shared-scratch and TLS-weakening entries.\n\n**Evidence**\n\n`third_party_attack`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}