Follow the guide to enable codebase context checks.

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Fix a potential NullReferenceException and incomplete XML escaping in the
Description property's getter by using System.Security.SecurityElement.Escape().

third_party/dotnet/devtools/src/generator/ProtocolDefinition/ProtocolDefinitionItem.cs [12-16]

 public string? Description
 {
-    get => InitialDescription?.Replace("<", "&lt;").Replace(">", "&gt;");
+    get => System.Security.SecurityElement.Escape(InitialDescription);
     set => InitialDescription = value;
 }

• Apply / Chat