diff options
| author |   Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-09-06 16:34:47 +0000 |
|---|---|---|
| committer | Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-09-06 16:34:47 +0000 |
| commit | 39d9810e128474aa64b19375652893d1795d7cbe (patch) | |
| tree | 1abd0d5a44f8261a92f9b15837188aa436cb18f7 /docs/Chapter4/Security.rst | |
| parent | 75fe466ce21fb3c5142bdaf70585d982af1c1b51 (diff) | |
VNFRQTS - Removing Security Req Batch 3
Including changes for VNFRQTS - 385, 388, 396, 397, 415, 416, 417, 418, 419, 421
Issue-ID: VNFRQTS-385
Change-Id: I5e864e7983283b0288178d670d51f54ef19e6c54
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
Diffstat (limited to 'docs/Chapter4/Security.rst')
| -rw-r--r-- | docs/Chapter4/Security.rst | 82 |
1 files changed, 0 insertions, 82 deletions
diff --git a/docs/Chapter4/Security.rst b/docs/Chapter4/Security.rst index 3899c8b..a56643d 100644 --- a/docs/Chapter4/Security.rst +++ b/docs/Chapter4/Security.rst @@ -662,56 +662,6 @@ API Requirements Multipurpose Internet Mail Extensions (MIME) type. Input files should be tested for spoofed MIME types. -.. req:: - :id: R-23772 - :target: VNF - :keyword: MUST - - The VNF **MUST** validate input at all layers implementing VNF APIs. - -.. req:: - :id: R-87135 - :target: VNF - :keyword: MUST - - The VNF **MUST** comply with NIST standards and industry - best practices for all implementations of cryptography. - -.. req:: - :id: R-02137 - :target: VNF - :keyword: MUST - - The VNF **MUST** implement all monitoring and logging as - described in the Security Analytics section. - -.. req:: - :id: R-15659 - :target: VNF - :keyword: MUST - - The VNF **MUST** restrict changing the criticality level of - a system security alarm to administrator(s). - -.. req:: - :id: R-19367 - :target: VNF - :keyword: MUST - - The VNF **MUST** monitor API invocation patterns to detect - anomalous access patterns that may represent fraudulent access or - other types of attacks, or integrate with tools that implement anomaly - and abuse detection. - -.. req:: - :id: R-78066 - :target: VNF - :keyword: MUST - - The VNF **MUST** support requests for information from law - enforcement and government agencies. - - VNF Security Analytics Requirements ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -812,15 +762,6 @@ Security Analytics Requirements as part of VNFs (e.g., PGW, MME). .. req:: - :id: R-20912 - :target: VNF - :keyword: MUST - - The VNF **MUST** support alternative monitoring capabilities - when VNFs do not expose data or control traffic or use proprietary and - optimized protocols for inter VNF communication. - -.. req:: :id: R-73223 :target: VNF :keyword: MUST @@ -870,13 +811,6 @@ Security Analytics Requirements The VNF **MUST** log logoffs. .. req:: - :id: R-08598 - :target: VNF - :keyword: MUST - - The VNF **MUST** log successful and unsuccessful changes to a privilege level. - -.. req:: :id: R-13344 :target: VNF :keyword: MUST @@ -1071,22 +1005,6 @@ Security Analytics Requirements enforcement and government agencies. .. req:: - :id: R-56786 - :target: VNF - :keyword: MUST - - The VNF **MUST** implement "Closed Loop" automatic implementation - (without human intervention) for Known Threats with detection rate in low - false positives. - -.. req:: - :id: R-25094 - :target: VNF - :keyword: MUST - - The VNF **MUST** perform data capture for security functions. - -.. req:: :id: R-04492 :target: VNF :keyword: MUST |