Get-TestimoXBaseline

Examples

Example 1: List every baseline catalog currently registered in the build

PS>

Get-TestimoXBaseline
        

Use this as the starting point when you need the exact baseline identifiers before drilling into a specific vendor/product/version.

Example 2: List only Microsoft baselines

PS>

Get-TestimoXBaseline -VendorIdFilter MSB
        

This narrows the catalog to Microsoft Security Baseline entries, which is helpful before a Windows Server review.

Example 3: Inspect controls for a specific baseline identifier

PS>

Get-TestimoXBaseline -Id 'MSB/Windows-Server-2025/1_0'
        

The returned controls can be piped into further filtering or exported for evidence packs.

Example 4: Inspect controls using vendor, product, and version selectors

PS>

Get-TestimoXBaseline -VendorId MSB -ProductId WindowsServer2025 -Version '1_0'
        

Example 5: Compare vendor guidance for Windows Server 2025 and return only the differences

PS>

Get-TestimoXBaseline -Compare -ProductId WindowsServer2025 -VersionWildcard '1_*' -OnlyDiff
        

This is useful when you want to see where CIS, STIG, and Microsoft guidance diverge before choosing a target baseline.

Example 6: Review crosswalk coverage across all TestimoX rules

PS>

Get-TestimoXBaseline -CrosswalkSummary
        

Example 7: Inspect vendor matches and external documentation for a single rule

PS>

Get-TestimoXBaseline -Crosswalk -RuleName DomainPasswordPolicy
Get-TestimoXBaseline -CrosswalkMatches -RuleName DomainPasswordPolicy
Get-TestimoXBaseline -CrosswalkDocs -RuleName DomainPasswordPolicy
        

These views help validate the evidence behind a rule before you publish guidance on the website.

Example 8: Suggest missing documentation links for a rule that still needs enrichment

PS>

Get-TestimoXBaseline -SuggestDocs -RuleName DomainPasswordPolicy -MinConfidence 0.75
        

Use this during crosswalk curation to spot likely PingCastle or Purple Knight references that are not yet linked.