{"id":251,"date":"2025-06-23T07:07:29","date_gmt":"2025-06-23T07:07:29","guid":{"rendered":"http:\/\/sreschool.com\/blog\/?p=251"},"modified":"2025-06-23T07:07:31","modified_gmt":"2025-06-23T07:07:31","slug":"incident-commander-in-devsecops-an-in-depth-tutorial","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/","title":{"rendered":"Incident Commander in DevSecOps: An In-Depth Tutorial"},"content":{"rendered":"\n

Introduction & Overview<\/h1>\n\n\n\n

What is Incident Commander<\/em>?<\/h3>\n\n\n\n

Incident Commander<\/strong> is a dedicated role or platform responsible for overseeing the end-to-end management of security, reliability, and operational incidents. In the context of DevSecOps<\/strong>, an Incident Commander ensures rapid coordination, communication, and resolution of incidents while maintaining compliance, security, and business continuity.<\/p>\n\n\n\n

\n

In modern organizations, this role is often supported by tools like PagerDuty<\/em>, FireHydrant<\/em>, Jeli<\/em>, or custom-built automation systems integrated into the CI\/CD lifecycle.<\/p>\n<\/blockquote>\n\n\n\n

History or Background<\/h3>\n\n\n\n
    \n
  • Originated in firefighting and disaster response<\/strong>\u2014the Incident Command System (ICS).<\/li>\n\n\n\n
  • Adopted by Site Reliability Engineering (SRE)<\/strong> teams at companies like Google to manage production outages.<\/li>\n\n\n\n
  • Evolved with DevSecOps<\/strong> to ensure incidents are managed with both security and agility<\/strong> in mind.<\/li>\n<\/ul>\n\n\n\n

    Why Is It Relevant in DevSecOps?<\/h3>\n\n\n\n
      \n
    • DevSecOps emphasizes continuous security<\/strong> and resilience<\/strong>.<\/li>\n\n\n\n
    • Incident Commanders reduce Mean Time to Detect (MTTD)<\/strong> and Mean Time to Respond (MTTR)<\/strong>.<\/li>\n\n\n\n
    • Facilitates cross-functional collaboration<\/strong> between dev, security, ops, and compliance teams.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      Core Concepts & Terminology<\/h2>\n\n\n\n

      Key Terms and Definitions<\/h3>\n\n\n\n
      Term<\/th>Definition<\/th><\/tr><\/thead>
      MTTD<\/strong><\/td>Mean Time to Detect \u2013 How quickly incidents are detected<\/td><\/tr>
      MTTR<\/strong><\/td>Mean Time to Resolve \u2013 How fast they are resolved<\/td><\/tr>
      Runbook<\/strong><\/td>A documented process for incident remediation<\/td><\/tr>
      Postmortem<\/strong><\/td>A retrospective analysis after incident resolution<\/td><\/tr>
      Severity Levels<\/strong><\/td>Classification of incidents (SEV-1 to SEV-5)<\/td><\/tr>
      Blameless Culture<\/strong><\/td>A DevSecOps value promoting learning, not blame<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      How It Fits Into the DevSecOps Lifecycle<\/h3>\n\n\n\n
      DevSecOps Phase<\/th>Role of Incident Commander<\/th><\/tr><\/thead>
      Plan<\/strong><\/td>Align incident response with threat models<\/td><\/tr>
      Develop<\/strong><\/td>Review code for potential failure points<\/td><\/tr>
      Build<\/strong><\/td>Ensure CI pipelines include security checks<\/td><\/tr>
      Release<\/strong><\/td>Validate rollback plans, alert configs<\/td><\/tr>
      Operate<\/strong><\/td>Lead and coordinate during outages<\/td><\/tr>
      Monitor<\/strong><\/td>Analyze signals to detect anomalies<\/td><\/tr>
      Respond<\/strong><\/td>Own incident handling, manage communication<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n

      Architecture & How It Works<\/h2>\n\n\n\n

      Components<\/h3>\n\n\n\n
        \n
      1. Incident Response Bot<\/strong> \u2013 Automated system that triggers alerts and assigns roles.<\/li>\n\n\n\n
      2. Commander Console<\/strong> \u2013 Central dashboard for monitoring and coordination.<\/li>\n\n\n\n
      3. Communication Hub<\/strong> \u2013 Slack, Teams, or Zoom war rooms.<\/li>\n\n\n\n
      4. Integrations Layer<\/strong> \u2013 Hooks into CI\/CD, observability tools, and security scanners.<\/li>\n<\/ol>\n\n\n\n

        Internal Workflow<\/h3>\n\n\n\n
        Detection \u2192 Triage \u2192 Assignment \u2192 Mitigation \u2192 Resolution \u2192 Postmortem\n<\/code><\/pre>\n\n\n\n
          \n
        1. An alert is generated (via Prometheus, AWS GuardDuty, etc.)<\/li>\n\n\n\n
        2. The incident is classified by severity<\/strong>.<\/li>\n\n\n\n
        3. The Incident Commander is assigned<\/strong>, often via automation.<\/li>\n\n\n\n
        4. The Commander coordinates teams, runs diagnostics, follows runbooks.<\/li>\n\n\n\n
        5. The incident is resolved, documented, and reviewed.<\/li>\n<\/ol>\n\n\n\n
          Architecture Diagram (Descriptive)<\/h3>\n\n\n\n
          [Cannot render image; textual architecture below]<\/strong><\/p>\n\n\n\n
          +------------------+        +-------------------+\n| Monitoring Tools | -----> | Incident Detection|\n+------------------+        +-------------------+\n                                     |\n                                     v\n                          +----------------------+\n                          | Incident Commander   |\n                          | Dashboard            |\n                          +----------------------+\n                                     |\n                   +----------------+----------------+\n                   |                                 |\n        +---------------------+           +---------------------+\n        | Slack\/Comm Channels |           | CI\/CD & Cloud Tools |\n        +---------------------+           +---------------------+\n<\/code><\/pre>\n\n\n\n
          Integration Points with CI\/CD or Cloud Tools<\/h3>\n\n\n\n
          Tool<\/th>Integration Purpose<\/th><\/tr><\/thead>
          GitHub\/GitLab<\/strong><\/td>Trigger incident reports on failed deployments<\/td><\/tr>
          PagerDuty<\/strong><\/td>Assign and notify responders<\/td><\/tr>
          AWS CloudWatch<\/strong><\/td>Signal anomalies or threshold breaches<\/td><\/tr>
          Jira\/ServiceNow<\/strong><\/td>Log incidents as tickets for tracking<\/td><\/tr>
          Terraform<\/strong><\/td>Automate infrastructure remediation<\/td><\/tr>
          OWASP ZAP\/SonarQube<\/strong><\/td>Feed security scan results into alerts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          \n\n\n\n
          Installation & Getting Started<\/h2>\n\n\n\n
          Basic Setup or Prerequisites<\/h3>\n\n\n\n
            \n
          • Cloud environment with IAM configured<\/li>\n\n\n\n
          • Slack\/MS Teams API access<\/li>\n\n\n\n
          • CI\/CD integration capability<\/li>\n\n\n\n
          • A tool like FireHydrant, PagerDuty, or a custom bot<\/li>\n\n\n\n
          • Python or Node.js runtime (for custom setups)<\/li>\n<\/ul>\n\n\n\n
            Hands-on: Beginner-Friendly Setup (FireHydrant Example)<\/h3>\n\n\n\n
            Step 1: Sign up and Configure Teams<\/h4>\n\n\n\n
            Visit https:\/\/www.firehydrant.com\/\n\u2192 Sign up\n\u2192 Create your teams (Dev, SecOps, etc.)\n<\/code><\/pre>\n\n\n\n
            Step 2: Connect Communication Channels<\/h4>\n\n\n\n
            \u2192 Go to Settings > Integrations\n\u2192 Connect Slack workspace\n\u2192 Authorize FireHydrant Bot\n<\/code><\/pre>\n\n\n\n
            Step 3: Add Monitoring & Alert Sources<\/h4>\n\n\n\n
            \u2192 Add integration with Datadog, CloudWatch, or Prometheus\n\u2192 Configure alert rules to trigger SEV-based incidents\n<\/code><\/pre>\n\n\n\n
            Step 4: Setup Runbooks<\/h4>\n\n\n\n
            name: Redis Failure\nsteps:\n  - Validate Redis pod health\n  - Restart Redis deployment\n  - Notify #db-alerts channel\n<\/code><\/pre>\n\n\n\n
            Step 5: Run a Simulated Incident<\/h4>\n\n\n\n
            \u2192 Trigger a test alert\n\u2192 Verify assignment to Incident Commander\n\u2192 Coordinate resolution\n<\/code><\/pre>\n\n\n\n
            \n\n\n\n
            Real-World Use Cases<\/h2>\n\n\n\n
            1. Production Outage Response (E-commerce)<\/strong><\/h3>\n\n\n\n
              \n
            • Incident:<\/strong> Database latency spike<\/li>\n\n\n\n
            • Action:<\/strong> Incident Commander initiates failover<\/li>\n\n\n\n
            • Outcome:<\/strong> Restores service in 15 minutes<\/li>\n<\/ul>\n\n\n\n
              2. Security Breach Containment (FinTech)<\/strong><\/h3>\n\n\n\n
                \n
              • Incident:<\/strong> Suspicious login pattern<\/li>\n\n\n\n
              • Action:<\/strong> Block offending IP, reset credentials<\/li>\n\n\n\n
              • Outcome:<\/strong> Contained breach before customer impact<\/li>\n<\/ul>\n\n\n\n
                3. Failed Deployment Recovery (SaaS)<\/strong><\/h3>\n\n\n\n
                  \n
                • Incident:<\/strong> CI pipeline deployed buggy release<\/li>\n\n\n\n
                • Action:<\/strong> Commander initiates rollback via GitHub Actions<\/li>\n\n\n\n
                • Outcome:<\/strong> Downtime limited to 5 minutes<\/li>\n<\/ul>\n\n\n\n
                  4. Compliance Violation Detection (Healthcare)<\/strong><\/h3>\n\n\n\n
                    \n
                  • Incident:<\/strong> PHI data exposed in logs<\/li>\n\n\n\n
                  • Action:<\/strong> Immediate alert, log redaction, notify compliance team<\/li>\n\n\n\n
                  • Outcome:<\/strong> Incident documented for HIPAA audit<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n
                    Benefits & \ud83d\udeab Limitations<\/h2>\n\n\n\n
                    Key Advantages<\/h3>\n\n\n\n
                      \n
                    • Faster response time<\/strong> to critical events<\/li>\n\n\n\n
                    • Improved cross-team coordination<\/strong><\/li>\n\n\n\n
                    • Audit trails<\/strong> and compliance-ready documentation<\/li>\n\n\n\n
                    • Security-first approach<\/strong> to incident handling<\/li>\n<\/ul>\n\n\n\n
                      Common Challenges<\/h3>\n\n\n\n
                        \n
                      • Role confusion<\/strong> in large teams<\/li>\n\n\n\n
                      • Alert fatigue<\/strong> due to poorly tuned rules<\/li>\n\n\n\n
                      • Complex integrations<\/strong> with legacy systems<\/li>\n\n\n\n
                      • Too much manual process<\/strong> without automation<\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n
                        Best Practices & Recommendations<\/h2>\n\n\n\n
                        Security Tips<\/h3>\n\n\n\n
                          \n
                        • Use role-based access control (RBAC)<\/strong> in incident systems.<\/li>\n\n\n\n
                        • Ensure encryption of communication logs<\/strong>.<\/li>\n\n\n\n
                        • Regularly audit runbooks<\/strong> for security-sensitive steps.<\/li>\n<\/ul>\n\n\n\n
                          Performance & Maintenance<\/h3>\n\n\n\n
                            \n
                          • Regularly simulate incidents (chaos drills)<\/li>\n\n\n\n
                          • Update integrations and token credentials<\/li>\n\n\n\n
                          • Monitor MTTR\/MTTD metrics and optimize response<\/li>\n<\/ul>\n\n\n\n
                            Compliance & Automation Ideas<\/h3>\n\n\n\n
                              \n
                            • Auto-generate Jira postmortem tickets<\/strong><\/li>\n\n\n\n
                            • Link SOC2 audit logs<\/strong> to incident trails<\/li>\n\n\n\n
                            • Automate runbook suggestions<\/strong> based on incident tags<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n
                              Comparison with Alternatives<\/h2>\n\n\n\n
                              Feature<\/th>FireHydrant<\/th>PagerDuty<\/th>Jeli<\/th>Custom Bot<\/th><\/tr><\/thead>
                              Slack Integration<\/td>\u2705<\/td>\u2705<\/td>\u2705<\/td>\u2705<\/td><\/tr>
                              Runbook Automation<\/td>\u2705<\/td>\u274c<\/td>\u274c<\/td>\u2705 (manual)<\/td><\/tr>
                              Postmortem Generator<\/td>\u2705<\/td>\u274c<\/td>\u2705<\/td>\u274c<\/td><\/tr>
                              Free Tier<\/td>\u2705 (limited)<\/td>\u2705 (basic)<\/td>\u274c<\/td>\u2705<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                              When to Choose Incident Commander Role or Tool<\/em><\/h3>\n\n\n\n
                                \n
                              • \u2705 You have regulated environments<\/strong> (HIPAA, SOC2)<\/li>\n\n\n\n
                              • \u2705 Need multi-team collaboration<\/strong><\/li>\n\n\n\n
                              • \u2705 Require auditable post-incident reviews<\/strong><\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n
                                Conclusion<\/h2>\n\n\n\n
                                Incident Commander roles and platforms are critical to a resilient and secure DevSecOps culture<\/strong>. They not only ensure fast response but also build a systematic learning loop via postmortems, alert tuning, and collaboration.<\/p>\n\n\n\n
                                Future Trends<\/h3>\n\n\n\n
                                  \n
                                • AI-driven incident prediction<\/strong><\/li>\n\n\n\n
                                • ChatOps-based automated playbooks<\/strong><\/li>\n\n\n\n
                                • Security-first incident platforms with zero trust<\/strong><\/li>\n<\/ul>\n\n\n\n
                                  \n\n\n\n
                                  <\/p>\n","protected":false},"excerpt":{"rendered":"
                                  Introduction & Overview What is Incident Commander? Incident Commander is a dedicated role or platform responsible for overseeing the end-to-end […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-251","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nIncident Commander in DevSecOps: An In-Depth Tutorial - SRE School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Incident Commander in DevSecOps: An In-Depth Tutorial - SRE School\" \/>\n<meta property=\"og:description\" content=\"Introduction & Overview What is Incident Commander? Incident Commander is a dedicated role or platform responsible for overseeing the end-to-end […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-23T07:07:29+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-23T07:07:31+00:00\" \/>\n<meta name=\"author\" content=\"priteshgeek\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"priteshgeek\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/\",\"url\":\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/\",\"name\":\"Incident Commander in DevSecOps: An In-Depth Tutorial - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2025-06-23T07:07:29+00:00\",\"dateModified\":\"2025-06-23T07:07:31+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Incident Commander in DevSecOps: An In-Depth Tutorial\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sreschool.com\/blog\/#website\",\"url\":\"https:\/\/sreschool.com\/blog\/\",\"name\":\"SRESchool\",\"description\":\"Master SRE. Build Resilient Systems. Lead the Future of Reliability\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sreschool.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\",\"name\":\"priteshgeek\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"caption\":\"priteshgeek\"},\"url\":\"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Incident Commander in DevSecOps: An In-Depth Tutorial - SRE School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/","og_locale":"en_US","og_type":"article","og_title":"Incident Commander in DevSecOps: An In-Depth Tutorial - SRE School","og_description":"Introduction & Overview What is Incident Commander? Incident Commander is a dedicated role or platform responsible for overseeing the end-to-end […]","og_url":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/","og_site_name":"SRE School","article_published_time":"2025-06-23T07:07:29+00:00","article_modified_time":"2025-06-23T07:07:31+00:00","author":"priteshgeek","twitter_card":"summary_large_image","twitter_misc":{"Written by":"priteshgeek","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/","url":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/","name":"Incident Commander in DevSecOps: An In-Depth Tutorial - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-23T07:07:29+00:00","dateModified":"2025-06-23T07:07:31+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/incident-commander-in-devsecops-an-in-depth-tutorial\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Incident Commander in DevSecOps: An In-Depth Tutorial"}]},{"@type":"WebSite","@id":"https:\/\/sreschool.com\/blog\/#website","url":"https:\/\/sreschool.com\/blog\/","name":"SRESchool","description":"Master SRE. Build Resilient Systems. Lead the Future of Reliability","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sreschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db","name":"priteshgeek","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","caption":"priteshgeek"},"url":"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/"}]}},"_links":{"self":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/251","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/comments?post=251"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/251\/revisions"}],"predecessor-version":[{"id":254,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/251\/revisions\/254"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=251"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=251"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=251"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}