Files
personaEngine2/tests/RuleEngine/UnknownNotFalse.Tests.ps1
T
dave cdc6bb33d3 Implement Stage A: rule engine, validation, audit, and safety gates
Completes 109 of 121 tasks. Every remaining task needs a tenant connection
(T055, T056, T101-T103) or an Azure Automation account (T115-T121).

  354 offline Pester tests      PASS
  Engine purity (Principle IV)  PASS
  Sanitization (SC-013)         PASS  (156 files)
  Graph module loaded in tests  none  (SC-008 holds)

What landed
  - Four-layer configuration validation with stable finding codes, covering
    every VR-002 and VR-003 condition, plus a 23-fixture invalid-config corpus
  - Run loop, audit records (NDJSON through a single sink), summaries,
    reconciliation, and exit codes 0-6
  - Persistence behind a single write-body builder whose result always has
    exactly one key
  - Invoke-PersonaEngine.ps1 and Edit-PersonaEngineConfig.ps1
  - Six docs, two pipelines, traceability matrix, V-5a and sanitization records

Three deviations from tasks.md, each recorded in its status block

  T033 is not in Resolve-UserPersona. evaluationErrorThreshold is run-level
  state and the rule engine is pure; a counter there would break Principle IV.
  It lives in New-PersonaRunCounter and is applied in the run loop.

  A new src/Engine/ layer holds Invoke-PersonaEngineRun. The entry script
  imports the manifest, which requires Microsoft.Graph.Authentication, so a
  loop living only inside it could not run on a machine without the Graph SDK
  and SC-004 could not be proven at all. The entry script is now a thin
  wrapper and what ships is what is tested.

  The invalid-config corpus is generated by a committed script, with the
  generated fixtures committed too, so a reviewer sees the fixture in the diff.

Defects found by running the code, not by reading it

  Group and role ID lists were double-wrapped: @(Get-PersonaGroupIdPage ...)
  around a comma-returned array collapsed every membership list into one
  bogus space-joined entry. That is a silent false non-match, exactly what
  FR-013 exists to prevent.

  A 403 whose status appears only in the exception message parsed as $null,
  which the retry policy treats as a transport error - five requests per
  account against a tenant already refusing. Status extraction now falls back
  to the message text, bounded to 400-599.

  The sanitization scan walked tracked files only, so it covered 34 of 156
  files and none of this phase's code. It now scans untracked non-ignored
  files too, and a negative control confirms it catches a planted leak.

  Test-Json reports one error per violating location, not first-failure-only
  as the V-5a draft claimed. Record and pin corrected.

Enforcement remains blocked on the V-4 security sign-off.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 21:48:19 -04:00

117 lines
5.0 KiB
PowerShell

#Requires -Modules @{ ModuleName = 'Pester'; ModuleVersion = '5.0.0' }
<#
Regression suite for the single most dangerous defect this system can have.
If a failed membership lookup is ever treated as "not a member", then:
notMemberOf <break-glass group> -> True
notMemberOf <tier 0 group> -> True
and a privileged account silently classifies as an ordinary user during a
transient Graph outage. The write then persists that downgrade to the
directory. Every assertion here exists to make that regression fail loudly.
#>
BeforeAll {
$repoRoot = Split-Path (Split-Path $PSScriptRoot -Parent) -Parent
foreach ($f in @(
'src/Normalization/New-PersonaMembershipRecord.ps1'
'src/Normalization/New-PersonaUserRecord.ps1'
'src/RuleEngine/Test-PersonaCondition.ps1'
'src/RuleEngine/Test-PersonaConditionGroup.ps1'
'src/RuleEngine/Test-PersonaRule.ps1'
'src/RuleEngine/Resolve-UserPersona.ps1'
)) { . (Join-Path $repoRoot $f) }
$script:tier0 = '00000000-0000-0000-0000-0000000000a0'
$script:failedLookupUser = New-PersonaUserRecord `
-AccountObjectId '00000000-0000-0000-0000-000000000001' `
-UserPrincipalName 'emergency-access-01@example.invalid' `
-Properties @{ Department = 'IT' } `
-StoredPersona 'Tier0-Admin' `
-Membership (New-PersonaMembershipRecord -DirectFailureReason 'Graph 503 after 5 attempts')
}
Describe 'A failed membership lookup is never a non-match (FR-013)' {
It 'does not satisfy notMemberOf' {
$result = Test-PersonaCondition -UserRecord $failedLookupUser -Condition ([pscustomobject]@{
type = 'membership'; operator = 'notMemberOf'; groupObjectIds = @($tier0)
})
$result | Should -Be 'Unknown'
$result | Should -Not -Be 'True' -Because 'treating unknown membership as "not a member" silently downgrades privileged accounts'
}
It 'does not satisfy memberOf either' {
Test-PersonaCondition -UserRecord $failedLookupUser -Condition ([pscustomobject]@{
type = 'membership'; operator = 'memberOf'; groupObjectIds = @($tier0)
}) | Should -Be 'Unknown'
}
It 'does not satisfy a role condition' {
Test-PersonaCondition -UserRecord $failedLookupUser -Condition ([pscustomobject]@{
type = 'role'; operator = 'memberOf'; roleIds = @('<TIER0-ROLE-TEMPLATE-ID>')
}) | Should -Be 'Unknown'
}
It 'prevents a notMemberOf rule from classifying a privileged account as ordinary' {
# The end-to-end version of the hazard: a "restricted user" rule defined as
# "not in the admin group" must not capture an account whose membership is
# simply unknown.
$restrictedRule = [pscustomobject]@{
id = 'R-100'; priority = 100; persona = 'Restricted-User'; enabled = $true
match = [pscustomobject]@{
operator = 'all'
conditions = @([pscustomobject]@{ type = 'membership'; operator = 'notMemberOf'; groupObjectIds = @($tier0) })
}
}
$result = Resolve-UserPersona -UserRecord $failedLookupUser -Rules @($restrictedRule)
$result.CalculatedPersona | Should -Not -Be 'Restricted-User'
$result.Outcome | Should -Be 'EvaluationError'
$result.StoredPersona | Should -Be 'Tier0-Admin'
}
}
Describe 'An empty successful lookup IS a legitimate non-match' {
BeforeAll {
# "Member of nothing" is a real, knowable answer and must evaluate normally.
# Over-applying the fail-safe would make every unaffiliated account an error.
$script:noGroupsUser = New-PersonaUserRecord `
-AccountObjectId '00000000-0000-0000-0000-000000000104' `
-UserPrincipalName 'drew.sparse@example.invalid' `
-Membership (New-PersonaMembershipRecord -DirectGroupObjectIds @() -DirectRetrieved)
}
It 'satisfies notMemberOf' {
Test-PersonaCondition -UserRecord $noGroupsUser -Condition ([pscustomobject]@{
type = 'membership'; operator = 'notMemberOf'; groupObjectIds = @($tier0)
}) | Should -Be 'True'
}
It 'does not satisfy memberOf' {
Test-PersonaCondition -UserRecord $noGroupsUser -Condition ([pscustomobject]@{
type = 'membership'; operator = 'memberOf'; groupObjectIds = @($tier0)
}) | Should -Be 'False'
}
It 'produces a normal Matched outcome, not an error' {
$restrictedRule = [pscustomobject]@{
id = 'R-100'; priority = 100; persona = 'Restricted-User'; enabled = $true
match = [pscustomobject]@{
operator = 'all'
conditions = @([pscustomobject]@{ type = 'membership'; operator = 'notMemberOf'; groupObjectIds = @($tier0) })
}
}
$result = Resolve-UserPersona -UserRecord $noGroupsUser -Rules @($restrictedRule)
$result.Outcome | Should -Be 'Matched'
$result.CalculatedPersona | Should -Be 'Restricted-User'
}
}