Review OSM for FedRamp Compliancy

[phillipgibson]

Please describe the Improvement and/or Feature Request Service meshes are an integral to many secured environments that have FedRamp compliancy. This issue will track the discovery of items under FedRamp that are specific to the OSM service mesh layer only. The output will be to create a backlog of items to complete to make OSM FedRamp compliant.

Scope (please mark with X where applicable)

• New Functionality [X]
• Install [ ]
• SMI Traffic Access Policy [ ]
• SMI Traffic Specs Policy [ ]
• SMI Traffic Split Policy [ ]
• Permissive Traffic Policy [ ]
• Ingress [ ]
• Egress [ ]
• Envoy Control Plane [ ]
• CLI Tool [ ]
• Metrics [ ]
• Certificate Management [ ]
• Sidecar Injection [ ]
• Logging [ ]
• Debugging [ ]
• Tests [ ]
• CI System [ ]
• Demo [ ]
• Project Release [ ]

Possible use cases Running OSM in secured environments with FedRamp compliancy needs.

[phillipgibson]

It appears having a cipher suite configuration may not assist with this and a specific Envoy image may need to be used that doesn't container additional cipher suites and only those specific to FIPS compliancy.

[github-actions[bot]]

This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update.

[github-actions[bot]]

Issue closed due to inactivity.