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
In some scenarios a STIG development project may contain a component that already has an official STIG.
For example a product include Kubernetes to run it's applications containers. Since Kubernetes has an official STIG it would make sense to be able to import that as a component to make any tweaks to or update any statuses if necessary to N/A/DNM/IM.
Since an official STIG only contains requirements marked "Applicable - Configurable" we would need to handle the remaining requirements and update their status to say N/A on import with a note that we don't know their true status but in this context these requirements are N/A.
The text was updated successfully, but these errors were encountered:
In some scenarios a STIG development project may contain a component that already has an official STIG.
For example a product include Kubernetes to run it's applications containers. Since Kubernetes has an official STIG it would make sense to be able to import that as a component to make any tweaks to or update any statuses if necessary to N/A/DNM/IM.
Since an official STIG only contains requirements marked "Applicable - Configurable" we would need to handle the remaining requirements and update their status to say N/A on import with a note that we don't know their true status but in this context these requirements are N/A.
The text was updated successfully, but these errors were encountered: