{"id":11414,"date":"2026-09-19T11:52:42","date_gmt":"2026-09-19T11:52:42","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=11414"},"modified":"2026-09-19T11:52:43","modified_gmt":"2026-09-19T11:52:43","slug":"common-devsecops-mistakes-businesses-should-avoid-early","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/","title":{"rendered":"Common DevSecOps Mistakes Businesses Should Avoid Early"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Introduction<\/h2>\n\n\n\n

Many growing businesses rush to build software faster. To keep up with competitors, they push new code to production daily. However, speed often comes at the cost of security.<\/p>\n\n\n\n

When a data breach happens, the financial and reputational damage can destroy a young company. To prevent this, teams adopt DevSecOps<\/strong>, which stands for Development, Security, and Operations.<\/p>\n\n\n\n

Instead of adding security at the very end of a project, DevSecOps weaves security into every phase of building software. Unfortunately, many companies make critical missteps when they first adopt this approach. This article explores the most common DevSecOps mistakes businesses make early on and how to avoid them.<\/p>\n\n\n\n

What Is DevSecOps?<\/h2>\n\n\n\n

DevSecOps<\/strong> is a software engineering approach that integrates security practices within the entire development lifecycle.<\/p>\n\n\n\n

    \n
  • Simple meaning:<\/strong> It means checking your code for security flaws as you write it, rather than waiting until the software is finished.<\/li>\n\n\n\n
  • Why it matters:<\/strong> Finding a security bug while writing code takes minutes to fix. Finding that same bug after the software is released to customers can take weeks and cost thousands of dollars.<\/li>\n\n\n\n
  • Example:<\/strong> Imagine baking a cake. Traditional security is tasting the cake only after it comes out of the oven to see if you accidentally added salt instead of sugar. DevSecOps is checking each ingredient as you mix the batter.<\/li>\n<\/ul>\n\n\n\n

    Why DevSecOps Matters for Growing Businesses<\/h2>\n\n\n\n

    As businesses digitize, software becomes the core of their operations. A single security vulnerability can expose customer data, lead to heavy regulatory fines, and break trust.<\/p>\n\n\n\n

    Many businesses believe security is only for large enterprises. In reality, startups and mid-sized companies are frequent targets for automated cyberattacks. Implementing DevSecOps early helps businesses build secure habits before their codebase grows too complex to manage.<\/p>\n\n\n\n

    Common DevSecOps Mistakes Businesses Should Avoid Early<\/h2>\n\n\n\n

    Adopting DevSecOps requires a shift in mindset, tools, and processes. Below are the most common mistakes companies make during the transition.<\/p>\n\n\n\n

    1. Treating Security as a Final Checkpoint<\/h3>\n\n\n\n

    Many organizations build their entire application and then hand it over to a separate security team for a final review just before launch.<\/p>\n\n\n\n

      \n
    • Why it happens:<\/strong> Companies view security as a gatekeeper rather than a partner.<\/li>\n\n\n\n
    • The problem:<\/strong> Finding dozens of security flaws right before a major product launch creates intense pressure. Teams either delay the release or push vulnerable code live just to meet deadlines.<\/li>\n\n\n\n
    • What to do instead:<\/strong> Integrate automated security tests directly into your CI\/CD pipeline<\/strong> (Continuous Integration and Continuous Delivery\u2014the automated process of building, testing, and deploying code). Catch vulnerabilities the moment a developer commits new code.<\/li>\n<\/ul>\n\n\n\n

      2. Buying Too Many Tools Without a Strategy<\/h3>\n\n\n\n

      Faced with security concerns, some businesses buy expensive commercial security tools hoping they will instantly solve all vulnerabilities.<\/p>\n\n\n\n

        \n
      • Why it happens:<\/strong> Vendors promise automated protection with minimal effort.<\/li>\n\n\n\n
      • The problem:<\/strong> Tools generate thousands of alerts. If the team does not know how to filter, prioritize, and fix these alerts, the software becomes overwhelmed with noise. Developers start ignoring the warnings entirely.<\/li>\n\n\n\n
      • What to do instead:<\/strong> Start small. Choose one or two reliable tools that fit your existing workflow. Master those before adding complex scanners.<\/li>\n<\/ul>\n\n\n\n

        3. Blaming Developers Instead of Fixing the Process<\/h3>\n\n\n\n

        When a security flaw slips into production, some organizations blame individual developers for writing insecure code.<\/p>\n\n\n\n

          \n
        • Why it happens:<\/strong> Management looks for a person to hold accountable for an incident.<\/li>\n\n\n\n
        • The problem:<\/strong> Blame creates fear. Developers stop reporting near-misses and focus solely on speed to avoid scrutiny, which worsens long-term security.<\/li>\n\n\n\n
        • What to do instead:<\/strong> Treat security bugs like regular software bugs. Look at the systemic failure: Did the developer lack training? Was the documentation unclear? Fix the process so the mistake cannot happen again.<\/li>\n<\/ul>\n\n\n\n

          4. Ignoring Open-Source Software Risks<\/h3>\n\n\n\n

          Modern software relies heavily on open-source libraries and packages to save development time. However, these third-party components can contain hidden vulnerabilities.<\/p>\n\n\n\n

            \n
          • Why it happens:<\/strong> Teams assume popular open-source code is automatically safe.<\/li>\n\n\n\n
          • The problem:<\/strong> If a widely used library has a security flaw, every application using it becomes vulnerable.<\/li>\n\n\n\n
          • What to do instead:<\/strong> Use SCA<\/strong> (Software Composition Analysis) tools to scan your project dependencies automatically and alert you when an open-source library needs an update.<\/li>\n<\/ul>\n\n\n\n

            Risks and Limitations of Poor DevSecOps Implementation<\/h2>\n\n\n\n

            Failing to implement DevSecOps correctly creates distinct operational risks:<\/p>\n\n\n\n

              \n
            • Developer Burnout:<\/strong> Flooding developers with false-positive security alerts leads to fatigue and frustration.<\/li>\n\n\n\n
            • Pipeline Bottlenecks:<\/strong> Poorly configured security scans that take hours to run defeat the purpose of rapid deployment.<\/li>\n\n\n\n
            • False Sense of Security:<\/strong> Relying purely on automated tools without human code review leaves logical business-logic flaws exposed.<\/li>\n<\/ul>\n\n\n\n

              Decision Framework: How to Start Your DevSecOps Journey<\/h2>\n\n\n\n

              If your business is new to DevSecOps, follow this step-by-step approach to avoid early failure:<\/p>\n\n\n\n

                \n
              1. Assess Your Current State:<\/strong> Review how your team currently writes, tests, and deploys code. Identify where security checks currently happen.<\/li>\n\n\n\n
              2. Educate the Team:<\/strong> Provide basic secure-coding training for developers so they understand common risks like injection attacks and weak authentication.<\/li>\n\n\n\n
              3. Automate Early Checks:<\/strong> Add a basic SAST<\/strong> (Static Application Security Testing\u2014automated scanning of source code for security vulnerabilities) tool into your code repository.<\/li>\n\n\n\n
              4. Gradually Expand:<\/strong> Once your team adapts to basic automated scanning, introduce dependency scanning and container security checks.<\/li>\n\n\n\n
              5. Measure and Improve:<\/strong> Track how long it takes your team to fix identified security vulnerabilities and refine your workflow over time.<\/li>\n<\/ol>\n\n\n\n

                Key Terms<\/h2>\n\n\n\n
                  \n
                • CI\/CD:<\/strong> An automated pipeline that builds, tests, and delivers software updates continuously.<\/li>\n\n\n\n
                • Vulnerability:<\/strong> A weakness in software code that an attacker could exploit.<\/li>\n\n\n\n
                • SAST:<\/strong> Automated tools that analyze source code for security flaws before the application runs.<\/li>\n\n\n\n
                • DAST:<\/strong> Automated tools that scan a running application from the outside to find security weaknesses.<\/li>\n\n\n\n
                • Container:<\/strong> A lightweight, standalone package of software that includes everything needed to run an application reliably.<\/li>\n\n\n\n
                • Remediation:<\/strong> The process of fixing a security vulnerability or system flaw.<\/li>\n\n\n\n
                • Compliance:<\/strong> Adhering to laws, regulations, and industry guidelines regarding data protection.<\/li>\n<\/ul>\n\n\n\n

                  FAQs<\/h2>\n\n\n\n

                  What is the main goal of DevSecOps?<\/h3>\n\n\n\n

                  The main goal is to embed security practices into every phase of the software development lifecycle, ensuring security is a shared responsibility rather than an afterthought.<\/p>\n\n\n\n

                  Does DevSecOps slow down software development?<\/h3>\n\n\n\n

                  Initially, setting up automated security checks takes time. However, over the long term, DevSecOps speeds up development by catching and fixing critical bugs early, preventing costly production rollbacks.<\/p>\n\n\n\n

                  Do small businesses need DevSecOps?<\/h3>\n\n\n\n

                  Yes. Small businesses are frequent targets for automated cyberattacks. Establishing basic security practices early prevents catastrophic data breaches as the business scales.<\/p>\n\n\n\n

                  Who is responsible for DevSecOps in a company?<\/h3>\n\n\n\n

                  Everyone is responsible. Developers write secure code, security teams define policies and provide guidance, and operations teams maintain secure infrastructure.<\/p>\n\n\n\n

                  What is the difference between DevOps and DevSecOps?<\/h3>\n\n\n\n

                  DevOps focuses on speed, collaboration, and automation between development and operations. DevSecOps adds security as a core pillar throughout that entire workflow.<\/p>\n\n\n\n

                  Conclusion<\/h2>\n\n\n\n

                  Adopting DevSecOps is not about buying expensive tools or slowing down your release cycle. It is about building a culture where security and speed work together. By avoiding common early mistakes\u2014such as treating security as a final checkbox or burying developers in alert noise\u2014businesses can build resilient, secure software that scales safely into the future.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  Introduction Many growing businesses rush to build software faster. To keep up with competitors, they push new code to production […]<\/p>\n","protected":false},"author":36,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11414","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\nCommon DevSecOps Mistakes Businesses Should Avoid Early - Cotocus<\/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:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Common DevSecOps Mistakes Businesses Should Avoid Early - Cotocus\" \/>\n<meta property=\"og:description\" content=\"Introduction Many growing businesses rush to build software faster. To keep up with competitors, they push new code to production […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/\" \/>\n<meta property=\"og:site_name\" content=\"Cotocus\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-19T11:52:42+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-19T11:52:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/09\/image-30.png\" \/>\n\t<meta property=\"og:image:width\" content=\"510\" \/>\n\t<meta property=\"og:image:height\" content=\"244\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Maria\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Maria\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/\"},\"author\":{\"name\":\"Maria\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/885dbedb9764f9e5755ec02fbde95459\"},\"headline\":\"Common DevSecOps Mistakes Businesses Should Avoid Early\",\"datePublished\":\"2026-09-19T11:52:42+00:00\",\"dateModified\":\"2026-09-19T11:52:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/\"},\"wordCount\":1187,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/image-30.png\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/\",\"name\":\"Common DevSecOps Mistakes Businesses Should Avoid Early - Cotocus\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/image-30.png\",\"datePublished\":\"2026-09-19T11:52:42+00:00\",\"dateModified\":\"2026-09-19T11:52:43+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/885dbedb9764f9e5755ec02fbde95459\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/image-30.png\",\"contentUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/image-30.png\",\"width\":510,\"height\":244},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/common-devsecops-mistakes-businesses-should-avoid-early\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common DevSecOps Mistakes Businesses Should Avoid Early\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\",\"name\":\"Cotocus\",\"description\":\"Shaping Tomorrow\u2019s Tech Today\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/885dbedb9764f9e5755ec02fbde95459\",\"name\":\"Maria\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c1fdd6016883bb62935d131d1ec28e736f88ef51258b30ef7ce2834bbf6035c7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c1fdd6016883bb62935d131d1ec28e736f88ef51258b30ef7ce2834bbf6035c7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/c1fdd6016883bb62935d131d1ec28e736f88ef51258b30ef7ce2834bbf6035c7?s=96&d=mm&r=g\",\"caption\":\"Maria\"},\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/author\\\/maria\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Common DevSecOps Mistakes Businesses Should Avoid Early - Cotocus","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:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/","og_locale":"en_US","og_type":"article","og_title":"Common DevSecOps Mistakes Businesses Should Avoid Early - Cotocus","og_description":"Introduction Many growing businesses rush to build software faster. To keep up with competitors, they push new code to production […]","og_url":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/","og_site_name":"Cotocus","article_published_time":"2026-09-19T11:52:42+00:00","article_modified_time":"2026-09-19T11:52:43+00:00","og_image":[{"width":510,"height":244,"url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/09\/image-30.png","type":"image\/png"}],"author":"Maria","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Maria","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#article","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/"},"author":{"name":"Maria","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/885dbedb9764f9e5755ec02fbde95459"},"headline":"Common DevSecOps Mistakes Businesses Should Avoid Early","datePublished":"2026-09-19T11:52:42+00:00","dateModified":"2026-09-19T11:52:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/"},"wordCount":1187,"commentCount":0,"image":{"@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/09\/image-30.png","inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/","url":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/","name":"Common DevSecOps Mistakes Businesses Should Avoid Early - Cotocus","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#primaryimage"},"image":{"@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/09\/image-30.png","datePublished":"2026-09-19T11:52:42+00:00","dateModified":"2026-09-19T11:52:43+00:00","author":{"@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/885dbedb9764f9e5755ec02fbde95459"},"breadcrumb":{"@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#primaryimage","url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/09\/image-30.png","contentUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/09\/image-30.png","width":510,"height":244},{"@type":"BreadcrumbList","@id":"https:\/\/www.cotocus.com\/blog\/common-devsecops-mistakes-businesses-should-avoid-early\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cotocus.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Common DevSecOps Mistakes Businesses Should Avoid Early"}]},{"@type":"WebSite","@id":"https:\/\/www.cotocus.com\/blog\/#website","url":"https:\/\/www.cotocus.com\/blog\/","name":"Cotocus","description":"Shaping Tomorrow\u2019s Tech Today","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cotocus.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/885dbedb9764f9e5755ec02fbde95459","name":"Maria","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/c1fdd6016883bb62935d131d1ec28e736f88ef51258b30ef7ce2834bbf6035c7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c1fdd6016883bb62935d131d1ec28e736f88ef51258b30ef7ce2834bbf6035c7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c1fdd6016883bb62935d131d1ec28e736f88ef51258b30ef7ce2834bbf6035c7?s=96&d=mm&r=g","caption":"Maria"},"url":"https:\/\/www.cotocus.com\/blog\/author\/maria\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11414","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/users\/36"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/comments?post=11414"}],"version-history":[{"count":1,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11414\/revisions"}],"predecessor-version":[{"id":11418,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11414\/revisions\/11418"}],"wp:attachment":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media?parent=11414"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/categories?post=11414"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/tags?post=11414"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}