27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Gatekeeper SHALL expose rule catalog metadata in audit output
|
|
Gatekeeper SHALL include the rule catalog version and enabled rule metadata in its validation result.
|
|
|
|
#### Scenario: Gatekeeper pass includes rule metadata
|
|
- **WHEN** Gatekeeper returns `status=pass`
|
|
- **THEN** the result SHALL include `rule_set_version`
|
|
- **AND** it SHALL include a rule metadata summary
|
|
|
|
#### Scenario: Gatekeeper fail includes rule metadata
|
|
- **WHEN** Gatekeeper returns `status=fail`
|
|
- **THEN** the result SHALL include `rule_set_version`
|
|
- **AND** it SHALL include a rule metadata summary
|
|
|
|
#### Scenario: Gatekeeper fallback pass includes rule metadata
|
|
- **WHEN** the Verifier input hook returns a fallback Gatekeeper pass because no Gatekeeper service is available
|
|
- **THEN** the result SHOULD still include the default rule set version and an empty or default rule metadata summary
|
|
|
|
### Requirement: Gatekeeper rule catalog SHALL remain deterministic
|
|
The Gatekeeper rule catalog SHALL configure metadata and simple parameters only; validation behavior SHALL remain deterministic Java code.
|
|
|
|
#### Scenario: Rule metadata is lightweight
|
|
- **WHEN** rule metadata is loaded
|
|
- **THEN** each enabled rule SHOULD expose an id, description, enabled flag, and default severity or relevant parameter
|
|
- **AND** rule metadata SHALL NOT execute dynamic scripts
|