Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POAMs Required Fields #5

Open
georgedias opened this issue Nov 9, 2022 · 0 comments
Open

POAMs Required Fields #5

georgedias opened this issue Nov 9, 2022 · 0 comments

Comments

@georgedias
Copy link
Collaborator

georgedias commented Nov 9, 2022

When adding a POAM with status value of "Ongoing" it looks like the following fields are required:

  • "vulnerabilitySeverityValue: The Severity is required.",
  • "relevanceOfThreat: The Relevance of Threat is required.",
  • "likelihood: The Likelihood is required.",
  • "impact: The Impact is required.",
  • "residualRiskLevel: The Residual Risk Level is required."
    These fields are now defined in the business logic of the eMASS API 3.9 as:
    *Note: Certain eMASS instances also require the Risk Analysis fields to be populated:
    • Severity
    • Relevance of Threat
    • Likelihood
    • Impact
    • Residual Risk Level
    • Mitigations

The field- "mitigation" is defined in the API ver 3.9 as optional, however when adding a new POAM, the server response states that it is a required field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant