FEAT: Adding AttackTechnique Registry#2101
Open
rlundeen2 wants to merge 1 commit into
Open
Conversation
Migrate AttackTechniqueRegistry from the legacy BaseInstanceRegistry stack onto the unified Registry + .instances design, mirroring the converter migration. Move the registry to pyrit/registry/components/, repoint all consumers/tests, and keep the buildable class catalog empty (the factory still owns construction). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
romanlutz
approved these changes
Jun 30, 2026
| import pandas as pd | ||
|
|
||
| from pyrit.registry.object_registries.attack_technique_registry import AttackTechniqueRegistry | ||
| from pyrit.registry.components.attack_technique_registry import AttackTechniqueRegistry |
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
2 participants
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.
Migrates
AttackTechniqueRegistryfrom the legacyBaseInstanceRegistrystack onto the unifiedRegistry+.instancesdesign, mirroring the converter migration. The registry now lives underpyrit/registry/components/, stores its pre-configuredAttackTechniqueFactoryinstances on theinstancesproperty, and has all consumers, tests, and docs repointed to the new path. The buildable class catalog stays intentionally empty for now (the factory still owns construction); it will be lit up later when the factory is decoupled into a buildable component.See the design doc / migration phases here (this is part of phase 5): https://gist.github.com/rlundeen2/f7960f7e8973fbb705b1b4bb48d8cdb2