Summary:

• The top-level Feature for this spike covers only regrouping existing hardening-related content that was previously distributed among the doc set into a hardening-specific guide
• The following resources should be used when discussing which existing content needs to be moved into the new hardening guide (provided by PM):
  • Initial analysis of the 17.1 security guide vs. what is currently documented in 18.0: https://docs.google.com/spreadsheets/d/1E9oAkB6KVtnwxf4-aya9ZHBvdvbtuxNFlx5P8yAiOVA/edit?gid=0#gid=0 Red are TripleO sections that will require new corresponding sections in 18.
  • Also, we made an early analysis pass of the current OSP 17.1 hardening guide, and where there is existing content in the RHOSO 18.0 documentation. the document currently requires further review. See: https://docs.google.com/document/d/1LmHnjQG7y6H1GpkeYrrA2611mOgcKJxkZ0RaLxJRtL4/edit?tab=t.0 
     
• In addition to compiling the list of topics to reorganize, this spike should also cover creating follow-up spikes or features under the top-level outcome for feature parity gaps on hardening the RHOSO environment.
  • These tickets need to be handed over to engineering for scoping, since they cannot be documented until the feature parity is covered. 
• If any existing tickets i.e. this story need to be closed or reworked, they should be done while completing the doc planning for the feature. The mini content journey should be used in the doc epic, not the parent feature.

TimeBox:

• This spike should be completed and all related tickets created before EOY
• The parent Feature of this spike will be accepted into FR5