Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/openraven/magpie

A Cloud Security Posture Manager or CSPM with a focus on security analysis for the modern cloud stack and a focus on the emerging threat landscape such as cloud ransomware and supply chain attacks.
https://github.com/openraven/magpie

aws cloud cloudsecurity cspm gcp security security-audit security-scanner security-testing security-tools security-vulnerability

Last synced: 21 days ago
JSON representation

A Cloud Security Posture Manager or CSPM with a focus on security analysis for the modern cloud stack and a focus on the emerging threat landscape such as cloud ransomware and supply chain attacks.

Host: GitHub
URL: https://github.com/openraven/magpie
Owner: openraven
License: apache-2.0
Created: 2021-02-17T18:44:49.000Z (almost 4 years ago)
Default Branch: main
Last Pushed: 2024-08-29T19:32:51.000Z (3 months ago)
Last Synced: 2024-08-30T21:01:35.137Z (3 months ago)
Topics: aws, cloud, cloudsecurity, cspm, gcp, security, security-audit, security-scanner, security-testing, security-tools, security-vulnerability
Language: Java
Homepage:
Size: 8.76 MB
Stars: 168
Watchers: 5
Forks: 24
Open Issues: 1
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

awesome-hacking-lists - openraven/magpie - A Cloud Security Posture Manager or CSPM with a focus on security analysis for the modern cloud stack and a focus on the emerging threat landscape such as cloud ransomware and supply chain attacks. (Java)

README

        # Magpie

#### [Open Raven's](https://openraven.com) Cloud Security Framework

- [What is Magpie](#what-is-magpie)

- [Overview](#overview)

  * [Magpie Architecture](#magpie-architecture)

- [Building Magpie](#building-magpie)

  * [Clone and build Magpie](#clone-and-build-magpie)

- [Running Magpie](#running-magpie)

  * [Configuration](#configuration)

    + [Overriding config.yaml](#overriding-configyaml)

    + [Multiple Overrides](#multiple-overrides)

  * [Running via Docker](#running-via-docker)

  * [Plugins](#plugins)

  * [Community Contributed Plugins](#community-contributed-plugins)

  * [Cloud Provider Status](#cloud-provider-status)

    + [AWS](#aws)

      - [Per region discovery](#per-region-discovery)

    + [GCP](#gcp)

    + [Azure](#azure)

  * [Saving data to PostgreSQL](#saving-data-to-postgresql)

## What is Magpie?

Magpie is a free, open-source framework and a collection of community developed plugins that can be used to build complete end-to-end security tools such as a CSPM or Cloud Security Posture Manager. The project was originally created and is maintained by Open Raven. We build commercial cloud native data security tools and in doing so have learned a great deal about how to discover AWS assets and their security settings at scale.

We also heard that many people were frustrated with their existing security tools that couldn't be extended  and couldn't work well with their other systems, so decided to create this Magpie framework and refactor and sync our core AWS commercial discovery code as the first plugin.

We plan to actively contribute additional modules to make Magpie a credible free open source alternative to commercial CSPM’s and welcome the community to join us in adding to the framework and building plugins.

## Overview

### Magpie Architecture

Magpie relies on plugins for all its integration capabilities.  They are the core of the framework and key to integration

with both cloud providers and downstream processing and storage.

*Magpie is essentially a series of layers separated by FIFOs.*

Depending on the configuration, these FIFOs are either **1) Java queues** (in the default configuration) or

**2) Kafka queues**.  Using Kafka queues allows Magpie to run in a distributed and highly scalable fashion where

each layer may exist on separate compute instances.

![Magpie Architecture](https://raw.githubusercontent.com/openraven/magpie-api/main/media/magpie_architecture.png?token=AAHX2PKUJYSKWMDS333MPSTALXTGC)

## Building Magpie

### Clone and build Magpie

```shell

git clone [email protected]:openraven/magpie.git

cd magpie

mvn clean install -DskipTests && mvn --projects magpie-cli assembly:single -DskipTests

```

The distribution zip file will be located in `magpie-cli/target/magpie-.zip`

Alternatively you can download the latest snapshot build by going to Action->(choose latest) and click the `magpie-cli` artifact,

which will download a zip distribution.  

By default Magpie has Maven building uber jars (shaded jars) to keep plugins from bringing potentially conflicting dependencies

onto the classpath.  Releases to Maven Central do not push uber jars. To build standard (non-shaded) jars you need to negate

the `uberjar` profile as such:

```

> mvn clean package -P -uberjar

```

## Running Magpie

*Java 17 is a prerequisite and must be installed to run Magpie.*

Out of the box Magpie supports AWS for the cloud provider and outputs discovery data to `stdout` in JSON format. The

AWS plugin utilizes the AWS Java SDK and will search for credentials as described in [Using Credentials](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html).

Assuming you have read credentials set up, you can start discovery by running:

```shell

./magpie-discovery.sh

```

Or from the Windows CMD line:

```

magpie-discovery.bat

```

From Windows Powershell:

```

./magpie-discovery.bat

```

### Configuration

Magpie allows for complex configurations to be enabled via the YAML-based config file.  This file has 3 primary sections:

- **Layers**: each of which contain 1 or more plugins and are surrounded by at least 1 FIFO

- **FIFOs**: which are either local (in-process Java queues) or Kafka queues

- **Plugins**: Each running plugin must be explictly.  A plugin-specific configuration object may reside in the `config` subsection.

The simplest Magpie configuration is shown below. This configuration enables AWS discovery with a JSON output to `stdout`. To write to a file

simply redirect the output:

```shell

./magpie.sh > output.json

```

Log messages are printed to `stderr` and will still show up as console output.

The simplest configuration:

```yaml

layers:

  enumerate:

    type: origin

    queue: default

    plugins:

      - magpie.aws.discovery

  output:

    type: terminal

    dequeue: default

    plugins:

      - magpie.json

fifos:

  default:

    type: local

plugins:

  magpie.aws.discovery:

    enabled: true

    config:

  magpie.json:

    enabled: true

    config:

  magpie.persist:

    enabled: false

    config:

      hostname: localhost

      port: 5432

      databaseName: db_name

      user: postgres

      password: postgres

```

#### Overriding config.yaml

It is possible to override *most* configuration values via environmental variables. This is most useful as an easy way to

script a Magpie instance on a one-per-aws-service basis.  To override configuration values, set an environmental variable

named `MAGPIE_CONFIG` and with a specially formed JSON object or array. For example, to perform an S3 *only* scan using

with the default configuration:

```bash

> MAGPIE_CONFIG="{'/plugins/magpie.aws.discovery/config/services': ['s3']}" ./magpie.sh

```

The value of `MAGPIE_CONFIG` must be a JSON object where the key is a [JSON Pointer](https://tools.ietf.org/html/rfc6901)

and the value is legal JSON which should be inserted into the location referenced by the pointer.

In the case where multiple overrides are required you may instead use an array of the above formatted objects as such:

```bash

> MAGPIE_CONFIG="[{'/plugins/magpie.aws.discovery/enabled', false }, {'/plugins/magpie.aws.discovery/config/services': ['s3']}]" ./magpie.sh

```

#### Multiple Overrides

If you have multiple values to set it may be easier to set multiple override variables instead of attempting to fit it

in a single env var.  Magpie will accept any and all environmental variables that match the regex `MAGPIE_CONFIG.*`. They

will be applied in Java's natural String ordering (lexicographic).  For example:

```bash

> export MAGPIE_CONFIG_1="[...]"

> export MAGPIE_CONFIG_2="[...]"

> ./magpie.sh

```

Both variables will be applied, if any duplicate JSON Pointers are provided the last one applied will win.

### Running via Docker

Builds on the `main` branch are automatically uploaded to quay.io under the `latest` tag.  See https://quay.io/repository/openraven/magpie for

all available tags. Once a stable public release is made this will also be available there.  The Docker image uses the

default config and provides no AWS credentials.

- Credentials can be added at runtime via volume mapping or passing environmental variables into the container.

- Configuration overrides can be done via environmental variable.

For example: to pass environmental variables for both credentials and configuration:

```bash

docker run -a stdout -a stderr \

--env MAGPIE_CONFIG="{'/plugins/magpie.aws.discovery/config/services': ['s3']}" \

-e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN \

quay.io/openraven/magpie:latest

```

The two `-a` arguments map both `stdout` and `stderr` to your local terminals, so you can redirect output as you would

with a local Mapgie execution.

### Plugins

### Community Contributed Plugins

If you've written a plugin you'd like listed please create a Pull Request with it listed here.

### Cloud Provider Status

#### AWS

Magpie supports AWS as a core plugin out of the box. Checked boxes are complete and available today, the unchecked are on the roadmap for completion. We have already built the code for all services in the list, but need to port them over from a previous framework.

- [x] EC2

- [x] S3

- [x] Athena

- [x] Batch

- [x] Backup

- [x] Cassandra

- [x] Cloudfront

- [x] Cloudsearch

- [x] Cloudtrail

- [x] CloudWatch

- [x] DynamoDB

- [x] EB

- [x] ECS

- [x] EFS

- [x] EKS

- [x] Elastic Cache

- [x] ELB

- [x] ELBv2

- [x] EMR

- [x] ESS

- [x] FSX

- [x] Glacier

- [x] GuardDuty  

- [x] IAM

- [x] KMS

- [x] Lakeformation

- [x] Lambda

- [x] Lightsail

- [x] QLDB

- [x] RDS

- [x] Redshift

- [x] Route 53

- [x] Secrets Manager

- [x] SecurityHub  

- [x] SNS

- [x] SSM

- [x] Storage Gateway

- [x] VPC

##### Per region discovery

By default the Magpie AWS Plugin will run discovery in all regions.  To narrow down discovery to a subset

of regions edit the plugins.magpie.aws.discovery.config.regions value to an array of desired region names, for example:

```yaml

plugins:

  magpie.aws.discovery:

    enabled: true

    config:

      regions:

        - us-east-2

        - us-east-1

```

#### GCP

Magpie also supports GCP as a core plugin out of the box. Checked boxes are complete and available today, the unchecked are on the roadmap for completion.

- [x]  AI Platform Data Labeling Service

- [x]  Access Approval

- [x]  AutoML

- [x]  BigQuery

- [ ]  BigQuery Connection API

- [x]  BigQuery Data Transfer Service

- [x]  BigQuery Reservation API

- [ ]  BigQuery Storage

- [x]  Cloud Asset Inventory

- [x]  Cloud Bigtable

- [x]  Cloud Billing

- [x]  Cloud Build

- [x]  Cloud Data Loss Prevention

- [x]  Cloud DNS

- [x]  Cloud Functions

- [x]  Cloud Key Management Service

- [x]  Cloud Logging

- [x]  Cloud Monitoring

- [x]  Cloud Monitoring Dashboards

- [ ]  Cloud Natural Language API

- [x]  Cloud OS Config

- [ ]  Cloud OS Login API

- [x]  Cloud Spanner

- [x]  Cloud Scheduler

- [x]  Cloud Storage

- [x]  Cloud Talent Solution Job Search

- [x]  Cloud Tasks

- [x]  Cloud Trace

- [x]  Cloud Translation

- [x]  Cloud Vision

- [x]  Compute Engine

- [x]  Container Analysis

- [x]  Data Catalog

- [x]  Dataproc

- [ ]  Datastore

- [x]  Dialogflow

- [x]  Error Reporting

- [ ]  Firestore

- [x]  Game Servers

- [x]  Google Kubernetes Engine

- [x]  Identity and Access Management

- [x]  Iam

- [x]  IoT Core

- [ ]  Media Translation

- [x]  Memorystore for Memcached

- [x]  Memorystore for Redis

- [ ]  Phishing Protection

- [x]  Pub/Sub

- [x]  Pub/Sub Lite

- [ ]  Recommendations AI

- [ ]  Recommender

- [x]  Resource Manager

- [x]  Secret Manager

- [ ]  Security Command Center

- [x]  Service Directory

- [ ]  Speech-to-Text

- [ ]  Text-to-Speech

- [ ]  Video Intelligence API

- [x]  VPC

- [ ]  Web Risk

- [x]  Web Security Scanner

- [x]  reCAPTCHA Enterprise

##### Authentication

To use this plugin save .json file with authentication key to file then set environment variable:

```

export GOOGLE_APPLICATION_CREDENTIALS=PATH_TO_CREDENTIALS_JSON_FILE

```

#### Azure

Magpie now contains experimental Azure support. The services supported are limited to:

- [x] SQL Servers

- [x] SQL Databases

- [x] Subscriptions

- [x] Storage Accounts

- [x] Storage Containers

While PG persistence works for Azure, there are no configuration rules written at this time and there is no estimate on when

such CSPM rules will exist for Azure.

##### Authentication

As with AWS and GCP, Magpie utilizes the Azure SDK to find and use credentials on the local system. Utilizing `az login` will

save credentials so that Magpie can use them.

### Saving data to PostgreSQL

By default, Magpie prints all discovered resources to standard out in JSON format. It's possible to modify this behaviour by changing

the default configuration.  The Magpie Peristence plugin comes bundled with Magpie but is in the disabled state by default.  To 

enable it  look at the following lines in the config file (config.yaml). set `enabled: true` and then modify the login

credentials as needed. Magpie will create all required tables at startup.

```yaml

magpie.persist:

    enabled: false

    config:

        hostname: localhost

        port: 5432

        databaseName: db_name

        user: postgres

        password: postgres

```