Jump to content
SUSE Rancher 2.6

Sysdig Secure DevOps Platform with SUSE Rancher

Getting Started


This document provides a brief introduction to Sysdig Secure DevOps Platform with SUSE Rancher, a SUSE One Partner Solution Stack.

SUSE One Partner Solution Stack

SUSE One Partner Solution Stacks are featured, SUSE-confirmed solutions, collaboratively developed with SUSE and partner components and designed to empower users to address their needs.

Disclaimer: Documents published as part of the series SUSE Technical Reference Documentation have been contributed voluntarily by SUSE employees and third parties. They are meant to serve as examples of how particular actions can be performed. They have been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. SUSE cannot verify that actions described in these documents do what is claimed or whether actions described have unintended consequences. SUSE LLC, its affiliates, the authors, and the translators may not be held liable for possible errors or the consequences thereof.

Author: Samip Parikh, Solutions Architect, SUSE
Author: Manuel Boira Cuevas, Strategic Partners Solutions Architect, Sysdig
Publication Date: November 09, 2021

1 Introduction

1.1 Motivation

SUSE Rancher enables you to accelerate your digital transformation by unifying your cloud native application landscape, ensuring consistent operations and workload management from core to cloud to edge. Sysdig Secure DevOps Platform gives you enhanced visibility and is designed to enable DevOps teams simplify security in cloud native environments, from development through production.

Sysdig Secure DevOps Platform provides a number of capabilities to help you securely run your applications in your SUSE Rancher Kubernetes landscape:

  • Secure the build – Automate image scanning in CI/CD pipelines and registries, efficiently flag vulnerabilities and owners, and block risky images.

  • Detect and respond to threats – Identify threats across containers and cloud services and prevent intrusion and lateral movement. Respond quickly and conduct forensics using detailed activity audits.

  • Continuously validate cloud configurations and compliance – Identify misconfigurations and compliance violations, and measure progress with detailed reports. Save time with out-of-the-box policies for standards such as PCI, NIST, HIPAA, and SOC 2.

  • Monitor and troubleshoot infrastructure and services – Maximize performance and availability using Kubernetes and cloud monitoring with full Prometheus compatibility.

1.2 Scope

This guide will help you take the first steps to integrate SUSE Rancher with Sysdig Secure DevOps Platform.

1.3 Audience

This document is intended for DevOps and DevSecOps engineers, security professionals, and developers who are responsible for enabling security across containers, clusters, and clouds.

2 Technical overview

The capabilities of Sysdig Secure and Sysdig Monitoring for SUSE Rancher are enabled by deploying the Sysdig agent on the nodes of your cluster. Relevant data and metadata are collected and available in the Sysdig SaaS back-end and accessible via the Sysdig user interface (UI). The Sysdig UI also provides the ability to customize aspects like policies, alerts, visualizations, permissions, etc.

Minimum requirements:

  • A Sysdig cloud account. You can get started with a free trial by visiting https://sysdig.com/start-free.

  • A SUSE Rancher cluster with a RKE, K3s, or any CNCF-certified Kubernetes cluster. Clusters can be located on-premises or in the cloud. You can also begin with community Rancher.

  • Outbound Internet access (at least port 6443). This allows collected information to be sent to the Sysdig back-end.

You can find the prerequisites for the Sysdig agent install on Kubernetes in the Sysdig documentation.

3 Installation

Get started by installing the Sysdig agent in your cluster. You can do so by using the SUSE Rancher Apps & Marketplace or by installing manually.

3.1 Install from the SUSE Rancher Apps & Marketplace

  1. From the top-left Rancher menu select Apps & Marketplace. From here, you will be taken to the Charts page.

    kubernetes gs rancher sysdig securedevops image marketplace overview
  2. Locate and select Sysdig Monitor & Secure, which will automate installation of the Sysdig agent via the Sysdig Helm chart.

  3. Specify a namespace, such as sysdig.

  4. Provide the Sysdig access key.

    kubernetes gs rancher sysdig securedevops image install 2
  5. Click Install. Once you initiate the Helm chart, within 15 minutes you should begin seeing data and activity in your Sysdig UI.

3.2 Install using generic/manual steps

To install the Sysdig agent using manual steps, follow the instructions in the Sysdig documentation.

4 Use case and demonstration

Sysdig Secure runtime security provides policy-driven detections, based on the Falco open-source project. Using predefined and custom policies, you can automate detection and alerting of suspicious and unexpected activity across containers, clusters, clouds.

In this example, you will create a custom runtime security policy that will detect when a shell is spawned in a container with a terminal attached. This can be practically useful, as commands executed with a terminal inside a container can be an indicator of an infiltration or attack.


For this example we are creating a simple custom rule that can be inhibited by other rules. We strongly recommend disallowing the predefined rule Suspicious Container Activity before adding the new rule (via Policies > Runtime Policies > Suspicious Container Activity).

After the experiment, reactivate the Suspicious Container Activity rule again.

4.1 Define and enable the customer runtime security policy

  1. Create the policy.

    1. Log into Sysdig Secure and, in the left panel, select Policies > Runtime Policies.

      kubernetes gs rancher sysdig securedevops image select runtime

      This opens the Runtime Policies page, where you can see the predefined policies.

      kubernetes gs rancher sysdig securedevops image Runtime Policies
    2. To create a custom policy, first select Add Policy in the upper right corner. Then, in the pop-up screen, select Workload Policy.

      kubernetes gs rancher sysdig securedevops image choose policy
    3. In the New Policy screen, enter a name and a description.

      kubernetes gs rancher sysdig securedevops image new policy name
      1. Keep the policy defaults: Enabled and a Severity level of High.

      2. You can customize the scope of this rule, indicating where it should apply. In this example, the scope is contained to a namespace, called terminal-shell-in-container. You can also set this to a broader scope, such as kubernetes.cluster.name, for example.

        kubernetes gs rancher sysdig securedevops image policy scope
  2. Assign a rule to use with the policy.

    1. Select Import from Library.

      kubernetes gs rancher sysdig securedevops image import
    2. Find and select Terminal shell in a container from the Rules Library, then click Import Rules.

      kubernetes gs rancher sysdig securedevops image rules library
    3. You should now see the Terminal shell in a container rule assigned to your policy.

  3. Specify the desired actions when a policy is triggered under Actions in the UI.

    1. Choose to kill, stop, or pause the container.

      For this example, leave this set to Nothing.

      For more information about Actions, see the Sysdig documentation.

    2. Set your desired notification channel.

      The default notification channel is email, but you can configure additional options under Settings > Notification Channels. For example, notifications can also be sent to a Slack Channel. Alternatively, leave this field blank.

  4. Enable recording of system call data surrounding an event.

    1. Turn on Capture.

    2. Provide a file name.

    3. Choose the number of seconds before and after the event to record.

      For example, 10 seconds before, and 20 seconds after the event.

      kubernetes gs rancher sysdig securedevops image capture config
  5. Create the policy by clicking Save.

4.2 Trigger a test event

You can trigger a test event to observe how Sysdig Secure detects the terminal shell in a container event and drill into the captured information to help you investigate the incident.

  1. Open a terminal shell from any container that is running in your SUSE Rancher cluster.

    1. Go to the Workloads section and access any pod with a running container.

      For this example, you can use the Sysdig agent pod.

      kubernetes gs rancher sysdig securedevops image open terminal shell from rancher ui 1
    2. From the menu on the right, click the Execute Shell option, and a new terminal shell will be shown at the bottom of the screen.

      kubernetes gs rancher sysdig securedevops image open terminal shell from rancher ui 2

This is sufficient for Sysdig to capture the event. You can type a few commands in the terminal to generate additional data that also will be captured by Sysdig Secure.

4.3 Viewing and investigating the event

Once the runtime security policy created above is triggered, you can view more information about the event in the Sysdig UI.

  1. Click Events.

    kubernetes gs rancher sysdig securedevops image events
  2. Click the "Terminal shell in a container" entry to open and view additional information about the event.

    You can scroll through this panel to see information, such as:

    • Information about the policy and rule(s) triggered.

    • Details about where the activity took place in your cluster (Scope), including which container as well as the detected process (in this case, bash).

    • “Tags” that indicate violated compliance standards, etc.

      kubernetes gs rancher sysdig securedevops image event details
  3. Dig deeper by clicking Respond at the top of this panel and selecting View Activity Audit.

    kubernetes gs rancher sysdig securedevops image view audit

    In the Activity Audit screen you will find details about the incident, including commands issued, file activity, network activity, and kube-exec activity.

    kubernetes gs rancher sysdig securedevops image activity audit
  4. Click any line item to see additional details, such as user, host, and scope.

    kubernetes gs rancher sysdig securedevops image Kubernetes details
  5. Click Captures from the top of the Activity Audit page to explore the capture file created when the incident triggered.

    kubernetes gs rancher sysdig securedevops image view capture 1
  6. Click the shovel icon to the right of the "Terminal shell in a container" capture file to open it with Sysdig Inspect.

    kubernetes gs rancher sysdig securedevops image view capture 2
  7. In the new tab, you are presented with a set of tiles that categorize the available details within the capture file. You can select any of these tiles to identify where the activity is within the timeline and drag the bars at the bottom to narrow into a specific area within the file.

    kubernetes gs rancher sysdig securedevops image Inspect
  8. Click one of the tiles, such as Executed Interactive Commands, to view further information about that particular activity and continue to drill down to investigate the incident.

    kubernetes gs rancher sysdig securedevops image IO streams capture

5 Summary

Security and monitoring are critical capabilities required to ensure uninterrupted operation and provide protection for applications and data running in your Kubernetes landscape.

Sysdig Secure DevOps Platform with SUSE Rancher enables you to embed security into your DevOps workflows, from build through production. With powerful automation to enhance Kubernetes and container security, you can quickly identify threats and reduce your risk profile.

6 Additional resources

Learn more about the capabilities of Sysdig Secure DevOps Platform with SUSE Rancher with these additional references.

8 GNU Free Documentation License

Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.


The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.


This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.


You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.


If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.


You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.

  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice.

  8. Include an unaltered copy of this License.

  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

  15. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties—​for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.


You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".


You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.


A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.


Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.


You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.


The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

ADDENDUM: How to use this License for your documents

Copyright (c) YEAR YOUR NAME.
   Permission is granted to copy, distribute and/or modify this document
   under the terms of the GNU Free Documentation License, Version 1.2
   or any later version published by the Free Software Foundation;
   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
   A copy of the license is included in the section entitled “GNU
   Free Documentation License”.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “ with…​Texts.” line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
   Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.

Print this page