{"id":383,"date":"2025-06-24T05:59:38","date_gmt":"2025-06-24T05:59:38","guid":{"rendered":"https:\/\/sreschool.com\/blog\/?p=383"},"modified":"2025-06-24T06:00:22","modified_gmt":"2025-06-24T06:00:22","slug":"escalation-chains-in-devsecops-a-complete-tutorial","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/","title":{"rendered":"Escalation Chains in DevSecOps: A Complete Tutorial"},"content":{"rendered":"\n

1. Introduction & Overview<\/strong><\/h1>\n\n\n\n

\ud83d\udd0d What Are Escalation Chains?<\/h3>\n\n\n\n

An Escalation Chain<\/strong> refers to a pre-defined sequence of steps and responsible individuals or roles that are triggered when a critical issue (such as a security alert, failed deployment, or policy violation) occurs and requires immediate attention.<\/p>\n\n\n\n

It ensures that:<\/p>\n\n\n\n

    \n
  • Unresolved incidents<\/strong> don\u2019t stay stagnant.<\/li>\n\n\n\n
  • The right stakeholders<\/strong> are notified in a timely manner.<\/li>\n\n\n\n
  • Accountability and response time<\/strong> improve.<\/li>\n<\/ul>\n\n\n\n

    \ud83d\udcda History or Background<\/h3>\n\n\n\n
      \n
    • Originated from ITIL and Incident Management frameworks<\/strong> in traditional IT Ops.<\/li>\n\n\n\n
    • Popularized in DevOps\/DevSecOps for automated security and reliability responses<\/strong>.<\/li>\n\n\n\n
    • With automated monitoring and alerting<\/strong>, the need to route unresolved issues efficiently became critical.<\/li>\n<\/ul>\n\n\n\n

      \ud83d\ude80 Why It\u2019s Relevant in DevSecOps<\/h3>\n\n\n\n

      In a DevSecOps pipeline, where security is integrated at every stage<\/strong>, escalation chains:<\/p>\n\n\n\n

        \n
      • Automate incident response<\/strong>.<\/li>\n\n\n\n
      • Help enforce compliance<\/strong> in regulated environments.<\/li>\n\n\n\n
      • Reduce MTTR (Mean Time to Resolution)<\/strong>.<\/li>\n\n\n\n
      • Allow collaborative triaging<\/strong> across development, security, and operations teams.<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n

        2. Core Concepts & Terminology<\/strong><\/h2>\n\n\n\n

        \ud83e\udde9 Key Terms and Definitions<\/h3>\n\n\n\n
        Term<\/th>Definition<\/th><\/tr><\/thead>
        Escalation Chain<\/strong><\/td>A tiered structure for notifying responsible personnel when an issue is unresolved after a certain time.<\/td><\/tr>
        Trigger Condition<\/strong><\/td>Event or status that initiates the escalation (e.g., failed security scan).<\/td><\/tr>
        Primary Responder<\/strong><\/td>First-level individual responsible for resolving the issue.<\/td><\/tr>
        SLA (Service Level Agreement)<\/strong><\/td>Defines response timelines before escalation is triggered.<\/td><\/tr>
        Notification Channel<\/strong><\/td>Medium used (Slack, Email, PagerDuty, SMS, etc.) to alert teams.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        \ud83d\udd04 How It Fits in the DevSecOps Lifecycle<\/h3>\n\n\n\n
        DevSecOps Phase<\/th>Escalation Role<\/th><\/tr><\/thead>
        Plan<\/strong><\/td>Alert on policy violation in code planning.<\/td><\/tr>
        Develop<\/strong><\/td>Escalate when secrets are found in commits.<\/td><\/tr>
        Build<\/strong><\/td>Trigger escalation if SBOM (Software Bill of Materials) scans fail.<\/td><\/tr>
        Test<\/strong><\/td>Alert QA\/security when vulnerabilities are found.<\/td><\/tr>
        Release<\/strong><\/td>Block release and escalate if compliance scan fails.<\/td><\/tr>
        Deploy<\/strong><\/td>Notify SREs if misconfigurations are detected in IaC.<\/td><\/tr>
        Monitor<\/strong><\/td>Alert Security Operations if anomaly is detected.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
        \n\n\n\n

        3. Architecture & How It Works<\/strong><\/h2>\n\n\n\n

        \ud83c\udfd7\ufe0f Components<\/h3>\n\n\n\n
          \n
        • Monitoring Tool (e.g., Prometheus, Snyk, AWS Security Hub)<\/strong><\/li>\n\n\n\n
        • Alert Manager (e.g., PagerDuty, Opsgenie, Alertmanager)<\/strong><\/li>\n\n\n\n
        • Escalation Rules Engine<\/strong> (Defines tiers and timings)<\/li>\n\n\n\n
        • Notification System<\/strong> (Slack, Email, SMS)<\/li>\n\n\n\n
        • Incident Management System<\/strong> (e.g., Jira, ServiceNow)<\/li>\n<\/ul>\n\n\n\n

          \ud83d\udd01 Internal Workflow<\/h3>\n\n\n\n
            \n
          1. Trigger<\/strong> \u2014 Event occurs (e.g., CVE found in container).<\/li>\n\n\n\n
          2. First Notification<\/strong> \u2014 Primary responder gets notified.<\/li>\n\n\n\n
          3. Timeout\/No Response<\/strong> \u2014 Escalation rule activates after SLA expiry.<\/li>\n\n\n\n
          4. Escalation Tier 2<\/strong> \u2014 Team lead\/manager alerted.<\/li>\n\n\n\n
          5. Final Escalation<\/strong> \u2014 Security head or CXO-level alert (for compliance breaches).<\/li>\n<\/ol>\n\n\n\n

            \ud83e\uddec Architecture Diagram Description<\/h3>\n\n\n\n
            \n

            Visualize the architecture as a layered flow:<\/p>\n<\/blockquote>\n\n\n\n

              \n
            • Event Source (CI\/CD tools, CloudWatch, SAST\/DAST)<\/strong>
              \u2193<\/li>\n\n\n\n
            • Alert Manager (defines rules)<\/strong>
              \u2193<\/li>\n\n\n\n
            • Escalation Engine<\/strong>\n
                \n
              • Tier 1 (Dev)<\/li>\n\n\n\n
              • Tier 2 (Security Lead)<\/li>\n\n\n\n
              • Tier 3 (CISO\/Manager)
                \u2193<\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • Notification Integrations<\/strong> (Email, Slack, PagerDuty)<\/li>\n<\/ul>\n\n\n\n

                \ud83d\udd17 Integration Points with CI\/CD and Cloud Tools<\/h3>\n\n\n\n
                Tool<\/th>Integration Point<\/th><\/tr><\/thead>
                GitHub Actions<\/td>Use on: failure<\/code> or on: pull_request<\/code> triggers.<\/td><\/tr>
                Jenkins<\/td>Integrate with Alertmanager via plugin or webhook.<\/td><\/tr>
                AWS<\/td>Use AWS CloudWatch + SNS + Lambda.<\/td><\/tr>
                Azure DevOps<\/td>Add logic to Azure Pipelines for escalation logic.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                \n\n\n\n

                4. Installation & Getting Started<\/strong><\/h2>\n\n\n\n

                \u2699\ufe0f Prerequisites<\/h3>\n\n\n\n
                  \n
                • CI\/CD Pipeline (Jenkins\/GitHub Actions)<\/li>\n\n\n\n
                • Monitoring\/Alert Tool (e.g., Prometheus, Sentry, AWS GuardDuty)<\/li>\n\n\n\n
                • Escalation\/Alerting Tool (e.g., PagerDuty, Opsgenie, VictorOps)<\/li>\n\n\n\n
                • Communication channels (Slack, Email SMTP)<\/li>\n<\/ul>\n\n\n\n

                  \ud83d\udc68\u200d\ud83d\udcbb Hands-On Setup (Beginner-Friendly Example with GitHub Actions + PagerDuty)<\/h3>\n\n\n\n

                  Step 1: Setup PagerDuty Escalation Policy<\/strong><\/p>\n\n\n\n

                    \n
                  • Create a service in PagerDuty.<\/li>\n\n\n\n
                  • Define escalation policy:\n
                      \n
                    • Tier 1: DevOps Engineer<\/li>\n\n\n\n
                    • Tier 2 (after 15 mins): Security Engineer<\/li>\n\n\n\n
                    • Tier 3 (after 30 mins): Security Manager<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

                      Step 2: GitHub Actions Workflow<\/strong><\/p>\n\n\n\n

                      name: Security Scan\n\non:\n  push:\n    branches:\n      - main\n\njobs:\n  scan:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Checkout code\n        uses: actions\/checkout@v3\n\n      - name: Run Trivy vulnerability scanner\n        uses: aquasecurity\/trivy-action@master\n        with:\n          image-ref: 'yourimage:latest'\n      \n      - name: Notify PagerDuty on failure\n        if: failure()\n        run: |\n          curl -X POST https:\/\/events.pagerduty.com\/v2\/enqueue \\\n            -H \"Content-Type: application\/json\" \\\n            -d '{\n              \"routing_key\": \"${{ secrets.PD_API_KEY }}\",\n              \"event_action\": \"trigger\",\n              \"payload\": {\n                \"summary\": \"Security vulnerability found in scan\",\n                \"severity\": \"critical\",\n                \"source\": \"GitHub Actions\"\n              }\n            }'\n<\/code><\/pre>\n\n\n\n
                      Step 3: Slack Notification via Webhook (optional)<\/strong><\/p>\n\n\n\n
                      curl -X POST -H 'Content-type: application\/json' \\\n--data '{\"text\":\"Escalation triggered: Vulnerability found.\"}' \\\nhttps://hooks.slack.com\/services\/TXXXX\/BXXXX\/XXXX\n<\/code><\/pre>\n\n\n\n
                      \n\n\n\n
                      5. Real-World Use Cases<\/strong><\/h2>\n\n\n\n
                      \ud83e\uddea Use Case 1: Vulnerability in Build Pipeline<\/h3>\n\n\n\n
                        \n
                      • Event<\/strong>: Snyk finds high-severity issue.<\/li>\n\n\n\n
                      • Escalation Chain<\/strong>: Dev \u2192 Security Lead \u2192 Compliance Officer.<\/li>\n<\/ul>\n\n\n\n
                        \ud83c\udfe5 Use Case 2: Healthcare App (HIPAA Compliance)<\/h3>\n\n\n\n
                          \n
                        • Event<\/strong>: PHI (Protected Health Info) leak detected.<\/li>\n\n\n\n
                        • Chain<\/strong>: DevOps \u2192 CISO \u2192 Legal\/Compliance.<\/li>\n<\/ul>\n\n\n\n
                          \u2601\ufe0f Use Case 3: Cloud Misconfiguration<\/h3>\n\n\n\n
                            \n
                          • Tool<\/strong>: AWS Config or Terraform Validator.<\/li>\n\n\n\n
                          • Escalation<\/strong>: Infrastructure Team \u2192 Cloud Security \u2192 CTO.<\/li>\n<\/ul>\n\n\n\n
                            \ud83d\uded2 Use Case 4: E-Commerce Site (PCI DSS)<\/h3>\n\n\n\n
                              \n
                            • Event<\/strong>: Unencrypted credit card storage flagged.<\/li>\n\n\n\n
                            • Chain<\/strong>: Dev \u2192 Security \u2192 Risk Officer.<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n
                              6. Benefits & Limitations<\/strong><\/h2>\n\n\n\n
                              \u2705 Key Benefits<\/h3>\n\n\n\n
                                \n
                              • Reduces incident response time<\/strong>.<\/li>\n\n\n\n
                              • Ensures clear ownership<\/strong>.<\/li>\n\n\n\n
                              • Boosts auditability and compliance<\/strong>.<\/li>\n\n\n\n
                              • Automates multi-tier notifications<\/strong>.<\/li>\n<\/ul>\n\n\n\n
                                \u26a0\ufe0f Limitations<\/h3>\n\n\n\n
                                Challenge<\/th>Description<\/th><\/tr><\/thead>
                                False Positives<\/td>May trigger unnecessary escalations.<\/td><\/tr>
                                Complex Setup<\/td>Needs tight integration across tools.<\/td><\/tr>
                                SLA Tuning<\/td>Misconfigured timers may delay response.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                \n\n\n\n
                                7. Best Practices & Recommendations<\/strong><\/h2>\n\n\n\n
                                \ud83d\udd10 Security Tips<\/h3>\n\n\n\n
                                  \n
                                • Use secure APIs\/webhooks for alerting.<\/li>\n\n\n\n
                                • Encrypt credentials and API keys.<\/li>\n<\/ul>\n\n\n\n
                                  \u2699\ufe0f Performance & Maintenance<\/h3>\n\n\n\n
                                    \n
                                  • Periodically review escalation policies<\/strong>.<\/li>\n\n\n\n
                                  • Run incident simulation drills<\/strong>.<\/li>\n<\/ul>\n\n\n\n
                                    \ud83d\udcdc Compliance Alignment<\/h3>\n\n\n\n
                                      \n
                                    • Link escalations with audit logs<\/strong> (Jira\/ServiceNow).<\/li>\n\n\n\n
                                    • Define response SLAs per compliance needs<\/strong> (e.g., SOC2, HIPAA).<\/li>\n<\/ul>\n\n\n\n
                                      \ud83e\udd16 Automation Ideas<\/h3>\n\n\n\n
                                        \n
                                      • Auto-create Jira tickets on each escalation.<\/li>\n\n\n\n
                                      • Use AI tools (like Opsgenie Intelligence) to auto-prioritize incidents.<\/li>\n<\/ul>\n\n\n\n
                                        \n\n\n\n
                                        8. Comparison with Alternatives<\/strong><\/h2>\n\n\n\n
                                        Approach<\/th>Escalation Chains<\/th>Manual Ticketing<\/th>AI-Powered Incident Response<\/th><\/tr><\/thead>
                                        Response Time<\/td>\u2705 Fast<\/td>\u274c Slow<\/td>\u2705 Fast<\/td><\/tr>
                                        Automation<\/td>\u2705 High<\/td>\u274c None<\/td>\u2705 Very High<\/td><\/tr>
                                        Config Complexity<\/td>\u26a0\ufe0f Medium<\/td>\u2705 Simple<\/td>\u26a0\ufe0f Complex<\/td><\/tr>
                                        Auditability<\/td>\u2705 Strong<\/td>\u26a0\ufe0f Depends<\/td>\u2705 Strong<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                        \ud83e\udd14 When to Choose Escalation Chains?<\/h3>\n\n\n\n
                                          \n
                                        • You want layered accountability<\/strong>.<\/li>\n\n\n\n
                                        • Need compliance-friendly response trail.<\/li>\n\n\n\n
                                        • Prefer tool-agnostic integration<\/strong> across CI\/CD pipelines.<\/li>\n<\/ul>\n\n\n\n
                                          \n\n\n\n
                                          9. Conclusion<\/strong><\/h2>\n\n\n\n
                                          Escalation Chains are vital to ensuring that security, operational, and compliance issues<\/strong> don\u2019t go unnoticed in a modern DevSecOps workflow. They automate the human layer of response, minimizing downtime, improving collaboration, and protecting sensitive infrastructure.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          <\/p>\n","protected":false},"excerpt":{"rendered":"
                                          1. Introduction & Overview \ud83d\udd0d What Are Escalation Chains? An Escalation Chain refers to a pre-defined sequence of steps and […]<\/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-383","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nEscalation Chains in DevSecOps: A Complete 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\/escalation-chains-in-devsecops-a-complete-tutorial\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Escalation Chains in DevSecOps: A Complete Tutorial - SRE School\" \/>\n<meta property=\"og:description\" content=\"1. Introduction & Overview \ud83d\udd0d What Are Escalation Chains? An Escalation Chain refers to a pre-defined sequence of steps and […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-24T05:59:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-24T06:00:22+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\/escalation-chains-in-devsecops-a-complete-tutorial\/\",\"url\":\"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/\",\"name\":\"Escalation Chains in DevSecOps: A Complete Tutorial - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2025-06-24T05:59:38+00:00\",\"dateModified\":\"2025-06-24T06:00:22+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Escalation Chains in DevSecOps: A Complete 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":"Escalation Chains in DevSecOps: A Complete 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\/escalation-chains-in-devsecops-a-complete-tutorial\/","og_locale":"en_US","og_type":"article","og_title":"Escalation Chains in DevSecOps: A Complete Tutorial - SRE School","og_description":"1. Introduction & Overview \ud83d\udd0d What Are Escalation Chains? An Escalation Chain refers to a pre-defined sequence of steps and […]","og_url":"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/","og_site_name":"SRE School","article_published_time":"2025-06-24T05:59:38+00:00","article_modified_time":"2025-06-24T06:00:22+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\/escalation-chains-in-devsecops-a-complete-tutorial\/","url":"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/","name":"Escalation Chains in DevSecOps: A Complete Tutorial - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-24T05:59:38+00:00","dateModified":"2025-06-24T06:00:22+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/escalation-chains-in-devsecops-a-complete-tutorial\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Escalation Chains in DevSecOps: A Complete 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\/383","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=383"}],"version-history":[{"count":2,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/383\/revisions"}],"predecessor-version":[{"id":385,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/383\/revisions\/385"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=383"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=383"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=383"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}