You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some tasks when exporting a component out of Vulcan to send to DISA that could be improved with a separate export feature that cleans up the output to make processing by DISA easier. The existing export to XLSX function could be copied and modified to support these additional requirements.
These items affect the export ONLY and do not change or update the data inside Vulcan.
For "Applicable - Configurable" controls remove any text in the "Status Justification", "Mitigation", and "Artifact Description" fields for the export.
For "Applicable - Inherently Meets" and "Not Applicable" controls remove any text in the "Mitigation" field for the export.
For "Not Applicable" controls remove any text in the "Artifact Description" field for the export
For "Not Applicable" controls update the check text in the export to "This requirement is NA for this technology."
For "Not Applicable" controls update the fix text in the export to "The requirement is NA. No fix is required."
For "Applicable - Inherently Meets" controls update the check text in the export to "The technology supports this requirement and cannot be configured to be out of compliance. The technology inherently meets this requirement."
For "Applicable - Inherently Meets" controls update the fix text in the export to "The technology inherently meets this requirement. No fix is required."
For "Applicable - Does Not Meet" controls update the check text in the export to "The technology does not support this requirement. This is an applicable-does not meet finding."
For "Applicable - Does Not Meet" controls update the fix text in the export to "This requirement is a permanent finding and cannot be fixed. An appropriate mitigation for the system must be implemented, but this finding cannot be considered fixed."
New option should be labeled "DISA Excel Export"
The text was updated successfully, but these errors were encountered:
There are some tasks when exporting a component out of Vulcan to send to DISA that could be improved with a separate export feature that cleans up the output to make processing by DISA easier. The existing export to XLSX function could be copied and modified to support these additional requirements.
These items affect the export ONLY and do not change or update the data inside Vulcan.
New option should be labeled "DISA Excel Export"
The text was updated successfully, but these errors were encountered: