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

Updates to emass client #6

Closed
33 tasks done
georgedias opened this issue Nov 11, 2022 · 0 comments · Fixed by #7
Closed
33 tasks done

Updates to emass client #6

georgedias opened this issue Nov 11, 2022 · 0 comments · Fixed by #7

Comments

@georgedias
Copy link
Collaborator

georgedias commented Nov 11, 2022

Axios

Check the OpenAPI auto generator for:

  • Verify why axios dependencies for the typescript client is set to 0.2.4
  • Check why is it using an offset of the axios code.

Client Code Base

  • Generate a python client
  • Add python client to Python Package Index (registry)

workflows

Change the following on publish-npm-gpr.yml

  • change actions/checkout@v1 to actions/checkout@v3
  • change the GPR npm publish public mitre-emass_client-.tgz to npm publish --access public mitre-emass_client-.tgz

Change the following on publish-npm-registry.yml

  • change actions/checkout@master to actions/checkout@v3
  • remove commented GPR steps

Change the following on publish-npm-gpr.yml and publish-npm-registry.yml

  • change runs-on: ubuntu-18.04 to runs-on: ubuntu-20.04
  • change actions/setup-node@v1 to actions/setup-node@v3

API endpoints Updates

V3.5

  • Added fields to Systems endpoint:
    isHVA - Boolean - [Read-Only] Indicates if the system contains High Value Assets. Does not display if value is null.

V3.6 to V3.9

  • Added fields to Systems endpoint:
Name Field
Is Financial Management isFinancialManagement
Is Reciprocity isReciprocity
Reciprocity Exemption reciprocityExemption
Cloud Computing cloudComputing
Cloud Type cloudType
Is SaaS isSaaS
Is PaaS isPaa
Is IaaS isIaaS
Other Service Models otherServiceModels
Need Date needDate
Overall Risk Score overallRiskScore
Is HRR isHRR
ATC Status atcStatus
ATC Date atcDate
ATC Termination Date atcTerminationDate
System Development Lifecycle systemDevelopmentLifeCycle
  • Added fields to CMMC Assessments endpoint:
Name Field
Highest Level Order Cage Code highestLevelOrderCageCode
Certification Unique ID highestLevelOrderCageCode
POAM poam
Overall Score overallScore
OSC Assessment Official Last Name oscAssessmentOfficialLastName
OSC Assessment Official First Name oscAssessmentOfficialFirstName
OSC Assessment Official Email oscAssessmentOfficialEmail
OSC Assessment Official Title oscAssessmentOfficialTitle

Renamed fields in CMMC Assessments endpoint:

  • • Unique Entity Identifier (uniqueEntityIdentifier) -> uei
  • • CageCodes (cageCode) → cageCodesInScope
  • • CertificateID (certificId) → assessmentId

Removed field from CMMC Assessments endpoint:

  • • DUNS -> duns

Added these Dashboard endpoints.

  • System Artifacts Summary
  • System Artifacts Details
  • System Sensor Hardware Summary
  • System Sensor Hardware Details
  • System Ports/Protocols Summary
  • System Ports/Protocols Detail
  • VA System FISMA Inventory Crypto Summary
  • VA System Threat Risks Summary
  • VA System Threat Sources Details
  • VA System Threat Architecture Details

V3.7

  • Added field to Systems endpoint:
    • Instance - instance

  • Renamed field in Systems endpoint:
    • Organization Name → owningOrganization

  • Removed field from Systems endpoint:
    • System Owner systemOwner

  • Added parameter to Dashboards endpoint:
    • Exclude Inherited → excludeInherited

Fix Artifacts Field

  • Field lastReviewedDate should be lastReviewDate type Date [Optional] Date artifact was last reviewed.Unix date format.

Fix Systems Field

The field authorizationStatus is set as an enumeration, limiting the data it can hold, however the specification states that:
* Some eMASS instances have custom Authorization Status values not captured in this list.

  • Make the field a free text entry
@georgedias georgedias linked a pull request May 18, 2023 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