guardian-severity

To classify severity for security findings, you provide the finding's zone, description, and evidence to an automated scoring system. The system then outputs a five-level severity classification and a recommendation for action.

Standardizing code quality finding severity is achieved by applying a formal, objective scoring matrix to the evidence. This reduces subjective assessments and ensures consistent, predictable outcomes across your development team's reviews.

Automated severity scoring works by evaluating the finding's zone, description, and evidence against formal criteria. It categorizes the security or software quality issue into one of five severity levels and generates an actionable recommendation.

You need to provide input data detailing the finding's zone, description, and evidence for automated security analysis severity classification. The system processes this information to output the appropriate severity level and review recommendation.

You can reduce subjective severity assessments in your software quality review process by using an automated classification system. It applies formal criteria to finding evidence to ensure consistent and predictable outcomes.

The severity scoring matrix requires complete input data detailing the finding's zone, description, and evidence to function correctly. It is designed specifically for software development teams using the Guardian role to assess findings.