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
Some controls (see controls/SV-257803.rb) have caveats in the check text for ISSO waivers for a package being present or not present.
We should determine if this language indicates that a control should have an explicit input for that package being a documented requirement, and if it does, update all controls that include one of the caveats.
The text was updated successfully, but these errors were encountered:
Yes, but each case should be considered carefully
But, for any of the "documented with the ISSO as an operational requirement" of which I saw 48 in v1r3.
create a sensible T/F logic input like "core_dumps_documented_by_ISSO_as_operational_requirement"
If set to True, set Impact to zero (which will calculate to be Not Applicable), and set a skip message like: "This requirement is not applicable since it is documented by the ISSO as an operational requirement"
AND run the tests anyway for situational awareness.
Some controls (see controls/SV-257803.rb) have caveats in the check text for ISSO waivers for a package being present or not present.
We should determine if this language indicates that a control should have an explicit input for that package being a documented requirement, and if it does, update all controls that include one of the caveats.
The text was updated successfully, but these errors were encountered: