From 20e52217472eb63933c86c0139498b10e76068ce Mon Sep 17 00:00:00 2001 From: Chris Compton Date: Wed, 1 Mar 2023 14:38:13 -0600 Subject: [PATCH] Require (Warn) port start and end when protocol is specified. (#1674) * Require (Warn) port start and end when protocol is specified. #1521 * Fix less than/equal entity in test. #1521 --- .../oscal_implementation-common_metaschema.xml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/metaschema/oscal_implementation-common_metaschema.xml b/src/metaschema/oscal_implementation-common_metaschema.xml index 29d57fec3a..75f09ebfc7 100644 --- a/src/metaschema/oscal_implementation-common_metaschema.xml +++ b/src/metaschema/oscal_implementation-common_metaschema.xml @@ -304,6 +304,21 @@ + + + + If a protocol is defined, it should include a start and end port range. To define a single port, the start and end should be the same value. + + + A start port exists, but an end point does not. To define a single port, the start and end should be the same value. + + + An end point exists, but a start port does not. To define a single port, the start and end should be the same value. + + + The port range specified has an end port that is less than the start port. + +

To be validated as a natural number (integer >= 1). A single port uses the same value for start and end. Use multiple 'port-range' entries for non-contiguous ranges.