Export OSCAL SSP

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • From the Authorization package overview record page, generate zip files and export the record's mapped content details in OSCAL format. To generate OSCAL SSP, the selected Authorization package must be in implemented state or after that. This action enables you to export your authorization package from CAM.

    Antes de Iniciar

    Role required:
    • sn_irm_cont_auth.admin
    • sn_irm_cont_auth.system_owner
    • sn_irm_cont_auth.authorization_official
    • sn_irm_cont_auth.info_system_sec_manager
    • sn_irm_cont_auth.info_system_sec_officer

    Procedimento

    1. Navigate to Workspaces > CAM Workspace.
    2. In the CAM Workspace, select the List icon (List).
    3. Select Authorization packages from the RMF list.
    4. From the list view, select the authorization package record for which to generate SSP files.
      Nota:
      The authorization package must be in the Implement, Assess, Authorize, or Monitor state to generate OSCAL SSP.
    5. To export OSCAL SSP, select Generate OSCAL SSP.
      Nota:
      If you’re using the Xanadu version, start from Step 5 in Export data in OSCAL format.
    6. Select Proceed in the pop-up window to commence generating the report.
      A message appears stating that the word file is being generated. A zip is generated which contains JSON files along with some diagrams. You’ll have to refresh the page before you download the JSON files.
    7. Select the Download OSCAL SSP from the Generate OSCAL SSP drop-down list to download the SSP zip file.Dowload oscal-ssp-zip.
      Importante:
      Verify that the pop-up blocker is turned off for the URL so that the SSP zip file is automatically downloaded to your local repository.

      You can view the catalog.json, overlay-catalog.json, profile.json, ssp.json files. Additionally, if any diagrams attached to the respective fields and boundary for the package are linked to it, then they’re also available in the contents of the zip. The diagrams can be a catalog dataflow diagram, network architecture diagram, or an authorization boundary diagram, available as png files in the zip.

      Nota:
      • The overlay-catalog.json file contains only the policies linked to the Authorization Package. If no catalog overlay is linked to the Authorization Package, the overlay-catalog.json file won’t be generated.
      • To customize the OSCAL behavior for export, see the OSCAL Model customization support [KB1650397] article in the Now Support Knowledge Base.

      For more information on OSCAL import error, see the OSCAL Import [KB1794095] article in the Now Support Knowledge Base.