Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Release of Sysdig Secure Integration #10841

Merged
Merged
Show file tree
Hide file tree
Changes from 20 commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
99e0229
Initialize Sysdig Package
nathanheffley Jul 25, 2024
9eb54e5
Built out initial handling of mappings and pipeline
cole-labar Aug 6, 2024
8f9a434
Added in test configurations and basics of documentation
cole-labar Aug 14, 2024
34fde0e
Updated mappings and refactored integration to use http over tcp. Adj…
cole-labar Aug 18, 2024
1999cc1
Updates to pipeline and test suite to work through system test proble…
cole-labar Aug 21, 2024
c04dc0d
Merge branch 'elastic:main' into feature/sysdig-initial-release
cole-labar Aug 21, 2024
230ddbd
Updated for feature flags
cole-labar Aug 21, 2024
b32447b
Updated to fix the system test issue and realign the event.original f…
cole-labar Aug 21, 2024
7203e30
First draft of viz dashboard and saved query
cole-labar Aug 22, 2024
a2cac62
Updated dashboard and screenshot for integration build process. Added…
cole-labar Aug 22, 2024
92f801f
Updated documentation and manifest
cole-labar Aug 22, 2024
8f60c5e
Updated fieldspec to include dynamic setting and remove flattened fields
cole-labar Aug 27, 2024
98938aa
Updated field mappings to better support visualizations
cole-labar Aug 27, 2024
a8efbf5
Adjusted sample logs to satisfy test runners
cole-labar Aug 27, 2024
03ab011
Updates based on PR comments
cole-labar Sep 3, 2024
36b1758
Shifted SysdigEvent fields into nested event for better consistency
cole-labar Sep 4, 2024
99cebae
Updated handling of cloud fields to ensure proper nesting
cole-labar Sep 4, 2024
91f2542
Updated manifest configs for http endpoint
cole-labar Sep 4, 2024
b2740c9
Updates for PR comments
cole-labar Sep 11, 2024
e30cb53
Updated manifest
cole-labar Sep 11, 2024
d0d1301
Dealt with ECS field issue and updated manifest
cole-labar Sep 12, 2024
894efbe
regenerated expected log file
cole-labar Sep 12, 2024
3715e3d
Merge branch 'main' into feature/sysdig-initial-release
cole-labar Sep 17, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
Expand Up @@ -331,6 +331,7 @@
/packages/symantec_endpoint_security @elastic/security-service-integrations
/packages/synthetics @elastic/obs-ux-infra_services-team
/packages/synthetics_dashboards @elastic/obs-ux-infra_services-team
/packages/sysdig @elastic/security-service-integrations
/packages/sysmon_linux @elastic/sec-linux-platform
/packages/system @elastic/obs-infraobs-integrations
/packages/system/changelog.yml @elastic/obs-infraobs-integrations @elastic/sec-linux-platform @elastic/sec-windows-platform
Expand Down
93 changes: 93 additions & 0 deletions packages/sysdig/LICENSE.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,93 @@
Elastic License 2.0

URL: https://www.elastic.co/licensing/elastic-license

## Acceptance

By using the software, you agree to all of the terms and conditions below.

## Copyright License

The licensor grants you a non-exclusive, royalty-free, worldwide,
non-sublicensable, non-transferable license to use, copy, distribute, make
available, and prepare derivative works of the software, in each case subject to
the limitations and conditions below.

## Limitations

You may not provide the software to third parties as a hosted or managed
service, where the service provides users with access to any substantial set of
the features or functionality of the software.

You may not move, change, disable, or circumvent the license key functionality
in the software, and you may not remove or obscure any functionality in the
software that is protected by the license key.

You may not alter, remove, or obscure any licensing, copyright, or other notices
of the licensor in the software. Any use of the licensor’s trademarks is subject
to applicable law.

## Patents

The licensor grants you a license, under any patent claims the licensor can
license, or becomes able to license, to make, have made, use, sell, offer for
sale, import and have imported the software, in each case subject to the
limitations and conditions in this license. This license does not cover any
patent claims that you cause to be infringed by modifications or additions to
the software. If you or your company make any written claim that the software
infringes or contributes to infringement of any patent, your patent license for
the software granted under these terms ends immediately. If your company makes
such a claim, your patent license ends immediately for work on behalf of your
company.

## Notices

You must ensure that anyone who gets a copy of any part of the software from you
also gets a copy of these terms.

If you modify the software, you must include in any modified copies of the
software prominent notices stating that you have modified the software.

## No Other Rights

These terms do not imply any licenses other than those expressly granted in
these terms.

## Termination

If you use the software in violation of these terms, such use is not licensed,
and your licenses will automatically terminate. If the licensor provides you
with a notice of your violation, and you cease all violation of this license no
later than 30 days after you receive that notice, your licenses will be
reinstated retroactively. However, if you violate these terms after such
reinstatement, any additional violation of these terms will cause your licenses
to terminate automatically and permanently.

## No Liability

*As far as the law allows, the software comes as is, without any warranty or
condition, and the licensor will not be liable to you for any damages arising
out of these terms or the use or nature of the software, under any kind of
legal claim.*

## Definitions

The **licensor** is the entity offering these terms, and the **software** is the
software the licensor makes available under these terms, including any portion
of it.

**you** refers to the individual or entity agreeing to these terms.

**your company** is any legal entity, sole proprietorship, or other kind of
organization that you work for, plus all organizations that have control over,
are under the control of, or are under common control with that
organization. **control** means ownership of substantially all the assets of an
entity, or the power to direct its management and policies by vote, contract, or
otherwise. Control can be direct or indirect.

**your licenses** are all the licenses granted to you for the software under
these terms.

**use** means anything you do with the software requiring one of your licenses.

**trademark** means trademarks, service marks, and similar rights.
3 changes: 3 additions & 0 deletions packages/sysdig/_dev/build/build.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
dependencies:
ecs:
reference: [email protected]
38 changes: 38 additions & 0 deletions packages/sysdig/_dev/build/docs/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Sysdig Integration
This integration allows for the shipping of [Sysdig](https://sysdig.com/) alerts to Elastic for observability and organizational awareness. Alerts can then be analyzed by using either the dashboard included with the integration or via the creation of custom dashboards within Kibana.

## Data Streams
The Sysdig integration collects one type of data stream: alerts.

**Alerts** The Alerts data stream collected by the Sysdig integration is comprised of Sysdig Alerts. See more details about Sysdig Alerts in [Sysdig's Alerts Documentation](https://docs.sysdig.com/en/docs/sysdig-monitor/alerts/). A complete list of potential fields used by this integration can be found in the [Logs reference](#logs-reference)

## Requirements

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it.
You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Sysdig must be configured to output alerts to a supported output channel as defined in [Setup](#setup). The system will only receive common fields output by Sysdig's rules, meaning that if a rule does not include a desired field the rule must be edited in Sysdig to add the field.

## Setup

For step-by-step instructions on how to set up an integration, see the [Getting started](https://www.elastic.co/guide/en/welcome-to-elastic/current/getting-started-observability.html) guide.

In order to capture alerts from Sysdig you **must** configure Sysdig to output Alerts as JSON via [HTTP](#http-input).

### HTTP Input

The HTTP input allows the Elastic Agent to receive Sysdig Alerts via HTTP webhook.

**Required:** To configure Sysdig to output JSON, you must set up as webhook notification channel as outlined in the [Sysdig Documentation](https://docs.sysdig.com/en/docs/administration/administration-settings/outbound-integrations/notifications-management/set-up-notification-channels/configure-a-webhook-channel/).

## Logs Reference

### alerts

Sysdig alerts can contain a multitude of various fields pertaining to the type of activity on the host machine.

{{ fields "alerts" }}

**Example event**

{{ event "alerts" }}
9 changes: 9 additions & 0 deletions packages/sysdig/_dev/deploy/docker/docker-compose.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
services:
sysdig-alerts-http:
image: docker.elastic.co/observability/stream:v0.16.0
volumes:
- ./sample_logs:/sample_logs:ro
environment:
- STREAM_PROTOCOL=webhook
- STREAM_ADDR=http://elastic-agent:9035/
command: log --start-signal=SIGHUP --delay=5s /sample_logs/sysdig.log
Loading