FEATURE REQUEST: Support for the USMC MCCAST POAM export in STIG Manager

[haynesjs]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

• We want to be able to export POAM from STIG Manger in MCCAST format and currently there is no drop down for that format. MCCAST is what the USMC uses for ATO packages and to import the format has to contain certain fields.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I work for the USMC and we need the POAM export feature in STIG Manager to have a drop down where you can select MCCAST. We can provide the fields that MCCAST requires or provide you a sample sheet with the fields we would like so there is seamless export and import from STIG-Manger strait into MCCAST which the USMC uses for ATO packages.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[cd-rite]

Hi @haynesjs Our Navy sponsors are typically reluctant to support processes that are not part of their baseline Navy-RMF pipeline, which uses eMASS. Sounds like that may be the equivalent to your MCCAST?

Even our Navy POAM creation is usually not a straight import into eMASS, since there are fields or worksheets that are outside of STIG Manager's purview and require further manipulation by RMF Validators.

That said, feel free to provide a sample file or field set showing what you are looking for. There may be some correspondence between that and something we can already generate.

[haynesjs]

MCCAST_POAM Example.csv

[haynesjs]

Above is an example of the fields we need for import to MCCAST. Just let me know. Thanks

[csmig]

Although the core team cannot work this feature at this time, perhaps those interested could open a PR that implements the feature in the API? The PR would need to address the following:

• provide an MCCAST POAM template XLSX that follows the example of the eMASS POAM template.
• add code that populates the template to the serializers.js source file
• Add a query parameter to the OAS definition of the Collection POAM endpoint to choose between eMASS and MCCAST style, defaulting to eMASS.
• Update this endpoint handler to accept the new query parameter and call the new template population functions

We'd be willing to work with the contributor during the process of getting the PR in good shape for merging. Afterwards, we could integrate the updated endpoint into the Web UI.