{"id":31818,"date":"2023-09-24T04:03:56","date_gmt":"2023-09-24T04:03:56","guid":{"rendered":"https:\/\/www.process.st\/templates\/disa-stig-compliance-checklist\/"},"modified":"2024-03-05T14:12:20","modified_gmt":"2024-03-05T14:12:20","slug":"disa-stig-compliance-checklist","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/disa-stig-compliance-checklist\/","title":{"rendered":"DISA STIG Compliance Checklist"},"content":{"rendered":"\n<section id=\"identify-the-system-resources-to-be-stig-reviewed\"> \n <h2>Identify the system resources to be STIG reviewed<\/h2>\n <div class=\"text-content\">\n   This task involves identifying the system resources that need to be reviewed for STIG compliance. These resources may include servers, databases, network devices, or other components of the system. The task plays a crucial role in determining the scope of the STIG review process and ensures that all relevant resources are included. The desired result is a comprehensive list of system resources to be reviewed. The task requires knowledge of the system architecture and understanding of the STIG requirements. Potential challenges may include identifying hidden or forgotten resources. To overcome this, consult system documentation, network diagrams, and engage with system owners or administrators. Required resources: system documentation, network diagrams, communication tools. \n <\/div> \n <div class=\"text-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> System resource name <\/label> \n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\"> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"installing-stig-viewer\"> \n <h2>Installing STIG Viewer<\/h2>\n <div class=\"text-content\">\n   This task involves installing the STIG Viewer tool, which is necessary for analyzing the system configuration against STIG rules. The installation of the tool is an essential step in the compliance process. It ensures that the system configuration can be assessed effectively. The desired result is a successfully installed STIG Viewer tool. To install the tool, follow the installation guide provided by DISA. Ensure that the system meets the hardware and software requirements specified in the guide. In case of any issues during the installation, refer to the troubleshooting section in the guide. Required resources: STIG Viewer installation guide, system meeting the hardware and software requirements. \n <\/div> \n<\/section> \n<section id=\"download-relevant-stig-checklist\"> \n <h2>Download relevant STIG checklist<\/h2>\n <div class=\"text-content\">\n   This task involves downloading the relevant STIG checklist for the system resources identified earlier. The checklist provides a comprehensive list of STIG rules specific to the system resources. It serves as a reference for assessing the system's compliance. The desired result is the downloaded STIG checklist. To download the checklist, visit the DISA STIG website and navigate to the appropriate category and resource. Click on the download link provided for the checklist. Required resources: internet access, DISA STIG website. \n <\/div> \n<\/section> \n<section id=\"analyzing-the-configuration-of-the-system-using-stig-viewer\"> \n <h2>Analyzing the configuration of the system using STIG Viewer<\/h2>\n <div class=\"text-content\">\n   This task involves analyzing the system configuration using the STIG Viewer tool. The analysis helps identify any non-compliant configurations and potential security vulnerabilities. The task is critical in assessing the system's compliance to STIG rules. The desired result is a comprehensive analysis report highlighting the non-compliant configurations and vulnerabilities. To perform the analysis, open the STIG Viewer tool and import the system configuration. Run the analysis tool and review the generated report. Required resources: STIG Viewer tool, system configuration file. \n <\/div> \n <div class=\"file-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Upload system configuration file <\/label> \n   <div class=\"file-container\"> <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button> \n   <\/div> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"evaluate-compliance-to-each-stig-rule\"> \n <h2>Evaluate compliance to each STIG rule<\/h2>\n <div class=\"text-content\">\n   This task involves evaluating the system's compliance to each STIG rule listed in the checklist. The evaluation helps assess the level of compliance and identify areas that require remediation. The task plays a crucial role in ensuring the system meets the required standards. The desired result is a comprehensive evaluation report with identified non-compliant items. To evaluate compliance, review each STIG rule listed in the checklist and assess the system's configuration accordingly. If a rule is found to be non-compliant, mark it as such in the evaluation report. Required resources: STIG checklist, evaluation report template. \n <\/div> \n<\/section> \n<section id=\"record-findings-and-create-draft-remediation-plan\"> \n <h2>Record findings and create draft remediation plan<\/h2>\n <div class=\"text-content\">\n   This task involves recording the findings from the evaluation of non-compliant items and creating a draft remediation plan. Recording the findings helps ensure that all identified non-compliant items are properly documented. Creating a draft remediation plan provides a roadmap for addressing the non-compliant items. The desired result is a recorded findings document and a draft remediation plan. To record the findings, create a document or spreadsheet and list each non-compliant item along with relevant details. To create a draft remediation plan, identify the steps required to remediate each non-compliant item and document them in a structured format. Required resources: findings document template, remediation plan template. \n <\/div> \n <div class=\"text-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Non-compliant item <\/label> \n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\"> \n  <\/div> \n <\/div> \n <div class=\"textarea-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Details <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"approval-remediation-plan-review\"> \n <h2>Approval: Remediation Plan Review<\/h2>\n <div class=\"approval-content\"> \n  <div class=\"header\"> \n   <div class=\"list-title\">\n    Will be submitted for approval:\n   <\/div> \n  <\/div> \n  <div class=\"approval-rule-subject-tasks-list\"> \n   <ul class=\"list\"> \n    <li> \n     <div class=\"approval-rule-subject-tasks-list-item\"> \n      <div class=\"item\"> \n       <div class=\"container\"> <span class=\"title\">Record findings and create draft remediation plan<\/span> \n        <div class=\"body\">\n         Will be submitted\n        <\/div> \n       <\/div> \n      <\/div> \n     <\/div> <\/li> \n   <\/ul> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"implement-remediation-actions-as-per-plan\"> \n <h2>Implement remediation actions as per plan<\/h2>\n <div class=\"text-content\">\n   This task involves implementing the remediation actions identified in the draft remediation plan. The remediation actions aim to address the non-compliant items and bring the system into compliance with STIG rules. The task is crucial in ensuring that the necessary actions are taken to resolve the identified issues. The desired result is the successful implementation of the remediation actions. To implement the remediation actions, follow the steps outlined in the draft remediation plan. Ensure that all necessary changes are made to the system configuration. Test the system after implementing the changes to validate their effectiveness. Required resources: draft remediation plan, access to system resources for making configuration changes. \n <\/div> \n <div class=\"multi-select-content form-field-content\"> \n  <div class=\"form-group\"> <label> Remediation actions <\/label> \n  <\/div> \n  <ul class=\"items\"> \n   <li class=\"item\"> \n    <div class=\"step-number-container\"> \n     <div class=\"step-number\">\n       1 \n     <\/div> \n    <\/div> \n    <div class=\"step-checkbox-container\"> \n     <div class=\"step-checkbox\"><\/div> \n    <\/div> \n    <div class=\"item-name-static\">\n      Apply security patches \n    <\/div> <\/li>\n   <li class=\"item\"> \n    <div class=\"step-number-container\"> \n     <div class=\"step-number\">\n       2 \n     <\/div> \n    <\/div> \n    <div class=\"step-checkbox-container\"> \n     <div class=\"step-checkbox\"><\/div> \n    <\/div> \n    <div class=\"item-name-static\">\n      Update system configurations \n    <\/div> <\/li>\n   <li class=\"item\"> \n    <div class=\"step-number-container\"> \n     <div class=\"step-number\">\n       3 \n     <\/div> \n    <\/div> \n    <div class=\"step-checkbox-container\"> \n     <div class=\"step-checkbox\"><\/div> \n    <\/div> \n    <div class=\"item-name-static\">\n      Disable unnecessary services \n    <\/div> <\/li>\n   <li class=\"item\"> \n    <div class=\"step-number-container\"> \n     <div class=\"step-number\">\n       4 \n     <\/div> \n    <\/div> \n    <div class=\"step-checkbox-container\"> \n     <div class=\"step-checkbox\"><\/div> \n    <\/div> \n    <div class=\"item-name-static\">\n      Configure access controls \n    <\/div> <\/li>\n   <li class=\"item\"> \n    <div class=\"step-number-container\"> \n     <div class=\"step-number\">\n       5 \n     <\/div> \n    <\/div> \n    <div class=\"step-checkbox-container\"> \n     <div class=\"step-checkbox\"><\/div> \n    <\/div> \n    <div class=\"item-name-static\">\n      Update user permissions \n    <\/div> <\/li> \n  <\/ul> \n <\/div> \n<\/section> \n<section id=\"reevaluate-compliance-to-each-stig-rule-post-remediation\"> \n <h2>Re-evaluate compliance to each STIG rule post remediation<\/h2>\n <div class=\"text-content\">\n   This task involves re-evaluating the system's compliance to each STIG rule after implementing the remediation actions. The re-evaluation helps ensure that the remediation actions have successfully addressed the non-compliant items. The task plays a crucial role in verifying the effectiveness of the remediation efforts. The desired result is a comprehensive re-evaluation report indicating the compliance status after remediation. To re-evaluate compliance, follow the same evaluation process used earlier. Review each STIG rule listed in the checklist and assess the system's configuration accordingly. Update the report with the new compliance status. Required resources: evaluation report template, updated system configuration. \n <\/div> \n<\/section> \n<section id=\"documentation-of-successful-remediations\"> \n <h2>Documentation of successful remediations<\/h2>\n <div class=\"text-content\">\n   This task involves documenting the successful remediations that have brought the system into compliance with STIG rules. Documentation helps ensure that the remediation efforts are properly recorded and can be referenced in the future. The task is crucial for maintaining an accurate record of system compliance. The desired result is a comprehensive documentation of successful remediations. To document the successful remediations, update the findings document created earlier with the details of the remediated non-compliant items. Include information such as the actions taken, date of completion, and any supporting documentation. Required resources: findings document template, supporting documentation. \n <\/div> \n<\/section> \n<section id=\"if-any-noncompliant-items-remain-create-a-poam-document\"> \n <h2>If any non-compliant items remain, create a POA&amp;M document<\/h2>\n <div class=\"text-content\">\n   This task involves creating a Plan of Action and Milestones (POA&amp;M) document if any non-compliant items remain after the remediation efforts. The POA&amp;M document outlines the specific steps that will be taken to address the remaining non-compliant items within a defined timeframe. The task is critical in ensuring that all non-compliant items are properly addressed and documented. The desired result is a completed POA&amp;M document. To create the POA&amp;M document, include the details of each remaining non-compliant item, proposed steps for remediation, responsible parties, and target completion dates. Required resources: POA&amp;M document template, access to non-compliant item details. \n <\/div> \n <div class=\"text-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Non-compliant item <\/label> \n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\"> \n  <\/div> \n <\/div> \n <div class=\"textarea-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Proposed steps for remediation <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea> \n  <\/div> \n <\/div> \n <div class=\"text-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Responsible party <\/label> \n   <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\"> \n  <\/div> \n <\/div> \n <div class=\"date-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Target completion date <\/label> \n   <div class=\"date-container\"> <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-calendar btn-icon\"><\/i> Date will be set here <\/button> \n   <\/div> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"submit-for-final-review-and-approval\"> \n <h2>Submit for final review and approval<\/h2>\n <div class=\"text-content\">\n   This task involves submitting the completed documentation, including the findings, remediation plan, re-evaluation report, and POA&amp;M (if applicable), for final review and approval. The final review and approval process ensures that all necessary documentation is accurate, complete, and compliant with DISA requirements. The desired result is the approval of the documentation for further certification processes. To submit for final review and approval, send the documentation to the designated reviewer or approval authority. Include a cover letter summarizing the documentation and any additional information required. Required resources: completed documentation, communication tools for submitting the documentation. \n <\/div> \n <div class=\"send-rich-email-content form-field-content\"> <!-- No Recipients --> <!-- No Recipients --> <!-- No Recipients --> \n  <div class=\"form-group subject\"> <label>Subject<\/label> \n   <p class=\"form-control-static\"> Documentation Submission - DISA STIG Compliance <\/p> \n  <\/div> \n  <div class=\"form-group body\"> <label>Body<\/label> <iframe srcdoc=\"<p>Dear [Reviewer\/Approver Name],<\/p><p>Please find attached the documentation related to the DISA STIG Compliance process. The submitted documentation includes:<\/p><ul><li>Findings document<\/li><li>Remediation plan<\/li><li>Re-evaluation report<\/li><li>POA&amp;amp;M (if applicable)<\/li><\/ul><p>Please review the attached documents and provide your valuable feedback and approval.<\/p><p>Thank you for your time and attention.<\/p>\n<style>*{font-family:Inter,&quot;Segoe UI&quot;,&quot;Roboto&quot;,&quot;Oxygen&quot;,&quot;Ubuntu&quot;,&quot;Cantarell&quot;,&quot;Fira Sans&quot;,&quot;Droid Sans&quot;,&quot;Helvetica Neue&quot;,system-ui,sans-serif}<\/style>\n\" sandbox=\"\"><\/iframe> \n  <\/div> \n  <div class=\"form-group\"> <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-envelope btn-icon\"><\/i> Send <\/button> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"approval-compliance-review\"> \n <h2>Approval: Compliance Review<\/h2>\n <div class=\"approval-content\"> \n  <div class=\"header\"> \n   <div class=\"list-title\">\n    Will be submitted for approval:\n   <\/div> \n  <\/div> \n  <div class=\"approval-rule-subject-tasks-list\"> \n   <ul class=\"list\"> \n    <li> \n     <div class=\"approval-rule-subject-tasks-list-item\"> \n      <div class=\"item\"> \n       <div class=\"container\"> <span class=\"title\">Re-evaluate compliance to each STIG rule post remediation<\/span> \n        <div class=\"body\">\n         Will be submitted\n        <\/div> \n       <\/div> \n      <\/div> \n     <\/div> <\/li> \n   <\/ul> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"prepare-system-for-certification-process\"> \n <h2>Prepare system for certification process<\/h2>\n <div class=\"text-content\">\n   This task involves preparing the system for the certification process after obtaining the necessary approvals. The certification process confirms that the system meets the required STIG compliance standards. The task is critical in ensuring that the system is ready for official certification. The desired result is a system prepared according to certification requirements. To prepare the system for certification, ensure that all identified non-compliant items have been addressed and documented. Validate the system configurations against the STIG checklist. Gather any additional supporting documentation required for the certification process. Required resources: approved documentation, system configurations, supporting documentation checklist for certification. \n <\/div> \n<\/section> \n<section id=\"submit-final-report-and-supporting-documentation\"> \n <h2>Submit final report and supporting documentation<\/h2>\n <div class=\"text-content\">\n   This task involves submitting the final report and supporting documentation for the completed STIG compliance process. The final report summarizes the entire process, including findings, remediation efforts, re-evaluation results, and approval status. Supporting documentation provides additional evidence of the system's compliance. The task ensures that all relevant information is compiled and submitted appropriately. The desired result is the successful submission of the final report and supporting documentation. To submit the final report and supporting documentation, compile all relevant documents into a single package. Include the final report, completed findings document, re-evaluation report, and any additional supporting documentation. Required resources: final report template, supporting documentation. \n <\/div> \n <div class=\"file-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Upload final report <\/label> \n   <div class=\"file-container\"> <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button> \n   <\/div> \n  <\/div> \n <\/div> \n <div class=\"file-field-content form-field-content\"> \n  <div class=\"form-group\"> <label> Upload supporting documentation <\/label> \n   <div class=\"file-container\"> <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button> \n   <\/div> \n  <\/div> \n <\/div> \n<\/section> \n<section id=\"conduct-periodic-reviews-and-updates-as-per-disa-guidelines\"> \n <h2>Conduct periodic reviews and updates as per DISA guidelines<\/h2>\n <div class=\"text-content\">\n   This task involves conducting periodic reviews and updates to ensure continued compliance with DISA guidelines. Periodic reviews help identify any changes in STIG requirements or system configurations that may impact compliance. Updates are necessary to address any newly identified non-compliant items or vulnerabilities. The task plays a crucial role in maintaining ongoing STIG compliance. The desired result is a documented review and update process. To conduct periodic reviews and updates, assign responsible individuals or teams for the task. Schedule regular review intervals and follow the guidelines provided by DISA. Document any changes or updates made during the process for future reference. Required resources: DISA guidelines, communication tools for coordinating reviews and updates. \n <\/div> \n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Identify the system resources to be STIG reviewed This task involves identifying the system resources that need to be reviewed for STIG compliance. These resources may include servers, databases, network devices, or other components of the system. The task plays a crucial role in determining the scope of the STIG review process and ensures that [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"\ud83d\udccb","cover_icon_url":"","tasks_count":"16","template_description":"","template_id":"iZtFoZ8NXjRXiWFH5jRKbQ","task_0":"Identify the system resources to be STIG reviewed","task_slug_0":"identify-the-system-resources-to-be-stig-reviewed","task_1":"Installing STIG Viewer","task_slug_1":"installing-stig-viewer","task_2":"Download relevant STIG checklist","task_slug_2":"download-relevant-stig-checklist","task_3":"Analyzing the configuration of the system using STIG Viewer","task_slug_3":"analyzing-the-configuration-of-the-system-using-stig-viewer","task_4":"Evaluate compliance to each STIG rule","task_slug_4":"evaluate-compliance-to-each-stig-rule","task_5":"Record findings and create draft remediation plan","task_slug_5":"record-findings-and-create-draft-remediation-plan","task_6":"Approval: Remediation Plan Review","task_slug_6":"approval-remediation-plan-review","task_7":"Implement remediation actions as per plan","task_slug_7":"implement-remediation-actions-as-per-plan","task_8":"Re-evaluate compliance to each STIG rule post remediation","task_slug_8":"reevaluate-compliance-to-each-stig-rule-post-remediation","task_9":"Documentation of successful remediations","task_slug_9":"documentation-of-successful-remediations","task_10":"If any non-compliant items remain, create a POA&M document","task_slug_10":"if-any-noncompliant-items-remain-create-a-poam-document","task_11":"Submit for final review and approval","task_slug_11":"submit-for-final-review-and-approval","task_12":"Approval: Compliance Review","task_slug_12":"approval-compliance-review","task_13":"Prepare system for certification process","task_slug_13":"prepare-system-for-certification-process","task_14":"Submit final report and supporting documentation","task_slug_14":"submit-final-report-and-supporting-documentation","task_15":"Conduct periodic reviews and updates as per DISA guidelines","task_slug_15":"conduct-periodic-reviews-and-updates-as-per-disa-guidelines","task_16":"","task_slug_16":"","task_17":"","task_slug_17":"","task_18":"","task_slug_18":"","task_19":"","task_slug_19":"","task_20":"","task_slug_20":"","task_21":"","task_slug_21":"","task_22":"","task_slug_22":"","task_23":"","task_slug_23":"","task_24":"","task_slug_24":"","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[74,57],"tags":[],"class_list":["post-31818","post","type-post","status-publish","format-standard","hentry","category-compliance","category-information-security"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/31818","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=31818"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/31818\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=31818"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=31818"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=31818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}