feat(policy-engine): add zero-expansion source optimization - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objectif
Ajoute une phase d’optimisation des sources strictement zéro-expansion, sans modifier les invariants du Policy Engine V2.
Architecture minimale
serviceKeystechniques sont identiques.Sécurité
Invariants inchangés :
Le libellé n’est jamais utilisé comme identité de fusion.
DNSTCP etDNSUDP restent séparés.Un subnet existant n’est jamais réutilisé sur simple inclusion ou densité. La cardinalité et l’appartenance doivent être exhaustivement identiques.
Résultat dataset réel
Ce résultat est volontaire : les trois doublons visuels observés sont en réalité
TCP:53contreUDP:53, et l’objetAVR-LAN-STATIONS-10.250.16.0/23couvre 512 adresses alors que la meilleure policy n’en prouve que 59. Les fusionner/réutiliser ouvrirait des permissions supplémentaires.Cas synthétique prouvé
Un objet
/30existant est réutilisé uniquement lorsque ses quatre adresses sont exactement les quatre sources autorisées. Une couverture 3/4 est refusée.Vérifications
Version applicative :
1.1.0.