{"id":77548,"date":"2024-08-02T16:48:26","date_gmt":"2024-08-02T14:48:26","guid":{"rendered":"https:\/\/www.skaylink.com\/?p=77548"},"modified":"2024-11-15T10:57:13","modified_gmt":"2024-11-15T09:57:13","slug":"trivy","status":"publish","type":"post","link":"https:\/\/www.skaylink.com\/en\/insights\/blog\/trivy\/","title":{"rendered":"Trivy: Secure Docker Containers in CI\/CD Pipelines"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Home<\/a><\/span><\/span><\/p>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Blog<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Secure Docker container creation in CI\/CD pipelines with Trivy vulnerability scanner <\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tImprove Docker container security in CI\/CD pipelines using the Trivy vulnerabiity scanner.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tAugust 2, 2024\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\"Picture\n\t\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tSkaylink\t\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t
\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In today\u2019s software development landscape, security is paramount. With the rise of containerization, ensuring the security of Docker images is essential to protect against vulnerabilities and potential exploits. CI\/CD pipelines provide a robust platform for automating software delivery. Integrating security scanning tools like Trivy fortifies your container creation process. In this blog post, we’ll explore how to improve the security of Docker containers in CI\/CD pipelines using Trivy.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Why Secure Docker containers matter <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Docker containers offer numerous benefits, including portability, scalability, and consistency across environments. But they also present security challenges. Vulnerabilities within container images can expose applications to various risks, such as data breaches, system compromises, or service disruptions. That\u2019s why it\u2019s crucial to address security concerns throughout the complete container lifecycle, from development to deployment.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Introducing Trivy <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Trivy is an open-source vulnerability scanner for containers and other artifacts, designed to quickly identify security issues within images. By using Trivy in your CI\/CD pipelines, you can automate vulnerability assessments and ensure that only secure container images are deployed into production environments.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Integrating Trivy into CI\/CD pipelines <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

CI\/CD pipelines offer a flexible and customizable approach to software delivery. By adding Trivy to your pipelines, you can seamlessly integrate vulnerability scanning into your container creation process. Here’s an overview of how you can do this:<\/p>

  1. Install Trivy:<\/strong>\u00a0Start by installing Trivy in your CI\/CD environment. You can either use Trivy as a standalone tool or incorporate it into a Docker container for easier integration.<\/li>
  2. Configure pipeline:<\/strong> Set up a CI\/CD pipeline for building Docker images. This pipeline should include stages for image creation, scanning with Trivy, and deployment.<\/li>
  3. Integrate Trivy scan:<\/strong> Add a step to your pipeline to execute Trivy and scan the Docker image for vulnerabilities. Trivy can be invoked through a simple command line interface, making it easy to incorporate into your pipeline scripts.<\/li>
  4. Analyze results:<\/strong> After the Trivy scan is complete, analyze the results to identify any vulnerabilities discovered. Trivy provides detailed reports, including information on the severity of each vulnerability and recommendations for mitigation.<\/li>
  5. Fail build on vulnerabilities:<\/strong> To enforce security standards, configure your pipeline to fail if any critical vulnerabilities are found during the Trivy scan. This ensures that only images that pass the Trivy scan are promoted to production.<\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t

    Setting up an Azure DevOps pipeline <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Create a YAML pipeline in Azure DevOps to build a Docker image, scan it with Trivy, and push it to a container registry if no vulnerabilities are detected.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    Step 1: Create a new pipeline <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t
    1. Log in to your Azure DevOps account and navigate to your project.<\/li>
    2. Go to \u201cPipelines\u201d > \u201cNew Pipeline\u201d and select \u201cAzure Repos Git\u201d as your source.<\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t

      Step 2: Define the YAML pipeline<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      Replace <YourContainerRegistry> and <YourDockerfile> with your actual container registry and Dockerfile names.<\/p>

      ((Codeblock begin))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      trigger:
      – main<\/p>

      pool:<\/span>\u00a0<\/span><\/p>

      \u00a0 vmImage: ‘ubuntu-latest’<\/span>\u00a0<\/span><\/p>

      \u00a0<\/span><\/p>

      steps:<\/span>\u00a0<\/span><\/p>

      \u00a0 – task: Docker@2<\/span>\u00a0<\/span><\/p>

      \u00a0\u00a0\u00a0 displayName: ‘Build Docker image’<\/span>\u00a0<\/span><\/p>

      \u00a0\u00a0\u00a0 inputs:<\/span>\u00a0<\/span><\/p>

      \u00a0\u00a0\u00a0\u00a0\u00a0 command: ‘build’<\/span>\u00a0<\/span><\/p>

      \u00a0\u00a0\u00a0\u00a0\u00a0 dockerfile: ‘<YourDockerfile>’<\/span>\u00a0<\/span><\/p>

      \u00a0\u00a0\u00a0\u00a0\u00a0 tags: ‘latest’<\/span>\u00a0<\/span><\/p>

      \u00a0\u00a0\u00a0\u00a0\u00a0 repository: ‘<YourContainerRegistry>\/<YourImageName>’<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      ((Codeblock end))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t
      \n\t\t\t\t\t

      Step 3: Add Trivy scanning <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      Add a step to your pipeline to run Trivy and scan your Docker image for vulnerabilities.<\/p>

      • Add the Trivy scanning step after building the Docker image:<\/li><\/ul>

        ((Codeblock begin))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        \u202f <\/span>– task: Bash@3<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f displayName: ‘Run Trivy vulnerability scan’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f inputs:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f targetType: ‘inline’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f script: |<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f # Install Trivy<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f Wget https:\/\/github.com\/aquasecurity\/trivy\/releases\/download\/v0.49.1\/trivy_0.49.1_Linux-64bit.tar.gz<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f tar zxvf trivy_0.49.1_Linux-64bit.tar.gz<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f sudo mv trivy \/usr\/local\/bin\/trivy<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f rm trivy_0.49.1_Linux-64bit.tar.gz<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f # Run Trivy scan<\/span>\u202f<\/span>\u00a0<\/span><\/p>

        \u202f\u202f\u202f\u202f\u202f\u202f\u202f trivy image –severity HIGH,CRITICAL –exit-code 1 <YourContainerRegistry>\/<YourImageName>:latest<\/span>\u202f<\/span>\u00a0<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        ((Codeblock end))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        In the scanning step, configure Trivy to close the scanning with exit code 1 if a high or critical vulnerability is found in the container. Exit code 1 lets Azure pipeline fail the step and stops pipeline execution. Trivy shows logs on findings and suggests fixed library versions.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t
        \n\t\t\t\t\t

        Step 4: Add Docker push <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        Add a step to your pipeline to push the docker image to the container registry. This step would only run if no vulnerabilities are found by Trivy.<\/p>

        • Add the Docker push step after the Trivy scan:<\/li><\/ul>

          ((Codeblock begin))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          – task: Docker@2<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f displayName: ‘Push Docker image to Container Registry’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f inputs:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f command: ‘push’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f tags: ‘latest’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f repository: ‘<YourContainerRegistry>\/<YourImageName>’<\/span>\u202f<\/span>\u00a0<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          ((Codeblock end))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t
          \n\t\t\t\t\t

          Complete YAML Pipeline <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Here’s the complete YAML pipeline with Trivy scanning:<\/p>

          ((Codeblock begin))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          trigger:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f – main<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f<\/span>\u00a0<\/span><\/p>

          pool:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f vmImage: ‘ubuntu-latest’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f<\/span>\u00a0<\/span><\/p>

          steps:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f – task: Docker@2<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f displayName: ‘Build Docker image’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f inputs:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f command: ‘build’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f dockerfile: ‘<YourDockerfile>’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f tags: ‘latest’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f repository: ‘<YourContainerRegistry>\/<YourImageName>’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f\u202f\u202f\u202f\u202f\u202f<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f – task: Bash@3<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f displayName: ‘Run Trivy vulnerability scan’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f inputs:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f targetType: ‘inline’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f script: |<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f # Install Trivy<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f wget https:\/\/github.com\/aquasecurity\/trivy\/releases\/download\/v0.49.1\/trivy_0.49.1_Linux-64bit.tar.gz<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f <\/span> tar zxvf trivy_0.49.1_Linux-64bit.tar.gz<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f sudo mv trivy \/usr\/local\/bin\/trivy<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f rm trivy_0.49.1_Linux-64bit.tar.gz<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f # Run Trivy scan<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f\u202f\u202f\u202f trivy image –severity HIGH,CRITICAL –exit-code 1 <YourContainerRegistry>\/<YourImageName>:latest<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f – task: Docker@2<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f displayName: ‘Push Docker image to Container Registry’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202f\u202f\u202f\u202f inputs:<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202fcommand: ‘push’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202ftags: ‘latest’<\/span>\u202f<\/span>\u00a0<\/span><\/p>

          \u202frepository: ‘<YourContainerRegistry>\/<YourImageName>’<\/span>\u202f<\/span>\u00a0<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          ((Codeblock end))<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t
          \n\t\t\t\t\t

          Benefits of secure container creation <\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Integrating Trivy into your CI\/CD pipelines provides several benefits:<\/p>

          • Early detection:<\/strong> Identify vulnerabilities in Docker images early in the development process, minimizing the risk of deploying insecure code.<\/li>
          • Automated security checks:<\/strong> Automate security scans within your CI\/CD pipeline, reducing the need for manual intervention and ensuring consistent security practices.<\/li>
          • Comprehensive reporting:<\/strong> Trivy provides detailed reports on discovered vulnerabilities, empowering teams to make informed decisions about risk mitigation strategies.<\/li>
          • Improved compliance:<\/strong> Meet compliance requirements by implementing security measures throughout the container lifecycle, from development to deployment.<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t
            \n\t\t\t\t\t

            Conclusion<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            Securing Docker containers is essential for safeguarding your applications and infrastructure against potential threats. By integrating Trivy into your CI\/CD pipeline, you can automate vulnerability scanning and ensure that only secure container images are deployed into production. With proactive security measures in place, you can enhance the resilience of your software systems and maintain the trust of your customers and stakeholders.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

            Improve Docker container security in CI\/CD pipelines using the Trivy vulnerabiity scanner.<\/p>\n","protected":false},"author":23,"featured_media":77549,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[100],"tags":[173],"class_list":["post-77548","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-development"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts\/77548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/comments?post=77548"}],"version-history":[{"count":104,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts\/77548\/revisions"}],"predecessor-version":[{"id":79816,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts\/77548\/revisions\/79816"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/media\/77549"}],"wp:attachment":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/media?parent=77548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/categories?post=77548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/tags?post=77548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}