This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

    Rapid Response: Installation

    With Rapid Response, Sysdig has introduced a way to grant designated Advanced Users in Sysdig Secure the ability to remote connect into a host directly from the Event stream and execute desired commands there.

    Rapid Response team members have access to a full shell from within the Sysdig Secure UI. Responsibility for the security of this powerful feature rests with you: your enterprise and your designated employees.

    See also: Rapid Response.

    Install and Configure Rapid Response


    • Sysdig Secure On-Premises 4.0+

      SaaS enablement available on a per-case basis at this time.

    • Have on hand:

      • Your Sysdig agent access key

      • Your Sysdig API endpoint (custom, depending on your on-prem installation)

      • A passphrase used to encrypt all traffic between the user and host.

        NOTE: Sysdig cannot recover this passphrase. If lost, a user will not be able to start a session, nor will any session logs be recoverable.

      Optionally, these can be added to the environment variables:

      export API_ENDPOINT=
      export API_TLS_SKIP_CHECK=false

    Install or Upgrade Sysdig Platform

    This feature is available as of Sysdig Platform v.4.0, on-premises. Be sure your system has been upgraded appropriately. SaaS enablement is on a per-case basis at this time; please discuss your situation with Sysdig Support.

    Install Host Component

    The Rapid Response agent can be installed as a Docker container or as a Kubernetes DaemonSet.

    As Docker Container

    1. Mount the host directories and binaries to gain access to the host.

      docker run --hostname $HOST_NAME -d --endpoint $API_ENDPOINT --access-key $ACCESS_KEY --password $PASSPHRASE
    2. Customize the Docker image.

      The container is simply bash shell. To add custom scripts without needing to mount the underlying host filesystem, you can bake this into the Docker container, e.g. by installing kubectl, gcloud, netstat, or another command-line utility.

      FROM AS base-image
      FROM alpine:3.13
      COPY --from=base-image /usr/bin/host /usr/bin/host
      # add custom scripts and other directives
      ENTRYPOINT ["host"]

    As Kubernetes DaemonSet

    1. Create a namespace and secrets for the Rapid Response agent:

      kubectl create ns rapid-response
      kubectl create secret generic sysdig-rapid-response-host-component-access-key --from-literal=access-key=$ACCESS_KEY -n rapid-response
      kubectl create secret generic sysdig-rapid-response-host-component-passphrase --from-literal=passphrase=$PASSPHRASE -n rapid-response
    2. Create the configmap and change the API_ENDPOINT parameter:

      echo "apiVersion: v1
      kind: ConfigMap
        name: sysdig-rapid-response-host-component
        api-endpoint: ${API_ENDPOINT}
        api-tls-skip-check: 'false'" | kubectl apply -n rapid-response -f -
    3. Deploy the DaemonSet.

      Note: The agent does not automatically have access to the host filesystem; there are several mounts commented-out in the manifest that must be uncommented to investigate the host.

      echo "# apiVersion: extensions/v1beta1  # If you are in Kubernetes version 1.8 or less please use this line instead of the following one
      apiVersion: apps/v1
      kind: DaemonSet
        name: sysdig-rapid-response-host-component
          app: sysdig-rapid-response-host-component
            app: sysdig-rapid-response-host-component
          type: RollingUpdate
              app: sysdig-rapid-response-host-component
            hostNetwork: true
              # Add custom volume here
              # Uncomment these lines if you'd like to map /root/ from the
              # host into the container.
              #- hostPath:
              #    path: /
              #  name: host-root-vol
              - name: sysdig-rapid-response-host-component-config
                  name: sysdig-rapid-response-host-component
                  optional: true
              - effect: NoSchedule
              - name: sysdig-rapid-response-host-component
                  # The privileged flag is necessary for OCP 4.x and other Kubernetes setups that deny host filesystem access to
                  # running containers by default regardless of volume mounts. In those cases, access to the CRI socket would fail.
                #  privileged: true
                imagePullPolicy: Always
                    cpu: 500m
                    memory: 500Mi
                    cpu: 250m
                    memory: 250Mi
                # Add custom volume mount here
                # Uncomment these lines if you'd like to map /root/ from the
                # host into the container.
                #- mountPath: /host
                #  name: host-root-vol
                  - name: API_ENDPOINT
                        name: sysdig-rapid-response-host-component
                        key: api-endpoint
                  - name: API_TLS_SKIP_CHECK
                        name: sysdig-rapid-response-host-component
                        key: api-tls-skip-check
                  - name: ACCESS_KEY
                        name: sysdig-rapid-response-host-component-access-key
                        key: access-key
                  - name: PASSWORD
                        name: sysdig-rapid-response-host-component-passphrase
                        key: passphrase" | kubectl apply -n rapid-response -f -

    Complete the Configuration

    After installation/upgrade, complete the following steps:

    • Request enablement of the feature from Sysdig Support.

    • Configure an S3 bucket for Rapid Response logs: If you are using the default Cassandra storage for Capture files, you will need to configure an AWS or custom S3 bucket to store Rapid Response log files after a session. If you have already configured an S3 bucket for Captures, then Rapid Response logs will be routed there automatically, into their own folder.

    • Manage the following port/firewall considerations:

      • Ensure the host component is able to reach the endpoint defined in API_ENDPOINT

      • Ensure there are no intermediate proxies that could enforce maximum time to live (since sessions could potentially have long durations)

      • Ensure that the host component can reach the object storage (S3 bucket) when configured.

    • Configure and use Rapid Response in the Sysdig Secure UI: See Rapid Response.