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

SAF CLI eMASSer Updates #3035

Open
14 of 16 tasks
georgedias opened this issue Nov 7, 2024 · 0 comments · May be fixed by #3282
Open
14 of 16 tasks

SAF CLI eMASSer Updates #3035

georgedias opened this issue Nov 7, 2024 · 0 comments · May be fixed by #3282

Comments

@georgedias
Copy link
Contributor

georgedias commented Nov 7, 2024

  • Change the emasser CLI Features and Capabilities documentation title to:

    • SAF CLI eMASS Client Features and Capabilities ?
    • SAF CLI eMASSer Features and Capabilities?
  • Update the README


SAF CLI

  • get controls - flag acronyms should be a string not Boolean
  • update the get dashboards EXAMPLES to: saf emasser get dashboards [dashboard name] [-o, --orgId] [options]
  • change flag options for scheduledCompletionDateStart, aliases: '-d' scheduledCompletionDateEnd, aliases: '-e'
  • in get workflow_definitions change the -i to -I (all Booleans are capitalized)
  • add register endpoint to the help file (https://saf-cli.mitre.org/docs/emasser)
  • test the post/put poams endpoints
  • saf emasser delete poams change the -P to -p
  • saf emasser delete milestones change the -M to -m
  • saf emasser delete artifacts change -F to -f

Need to update the following endpoint calls (plus all other defined in the v3.22).

  • The field role should NOT be an enum in get system-roles (query parameter)
  • Added assessmentProcedures to get test-results, get poams, get artifacts (query parameter)
  • Evaluate the get artifacts export endpoint - file is exported to the temp directory
  • POA&Ms - new required field identifiedInCFOAuditOrOtherReview (VA only) (PUT/POST)

Warn user about POAM required fields when status is "Ongoing"

  • Certain eMASS instances require the Risk Analysis fields to be populated:
  • Severity (severity)
  • Relevance of Threat (relevanceOfThreat)
  • Likelihood (likelihood)
  • Impact (impact)
  • Residual Risk Level (residualRiskLevel)
  • Mitigations (mitigation)
@georgedias georgedias changed the title eMASS Client Updates SAF CLI eMASSer Updates Feb 14, 2025
@georgedias georgedias linked a pull request Feb 14, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant