JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 712
  • Score
    100M100P100Q117454F
  • License MIT

Alert rule packages for the JupiterOne platform

Package Exports

  • @jupiterone/jupiterone-alert-rules
  • @jupiterone/jupiterone-alert-rules/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@jupiterone/jupiterone-alert-rules) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

JupiterOne Alert Rule Packs

This project contains default rule packs that can be provisioned to your JupiterOne account via the included CLI utility.

Rule Packs

  • rule-packs/aws-config.json

    Alert rules for AWS configuration audit

  • rule-packs/aws-threat.json

    Alert rules for AWS threat monitoring

  • rule-packs/gcp.json

    Alert rules for Google Cloud Platform

  • rule-packs/azure-config.json

    Alert rules for Azure configuration audit

  • rule-packs/azure.json

    Commonly used Azure alert rules

  • rule-packs/gcp.json

    Commonly used GCP alert rules

  • rule-packs/common-alerts.json

    Commonly used alert rules

  • rule-packs/critical-assets.json

    Alert rules to monitor changes to and risks of critical assets

  • rule-packs/devops.json

    Commonly used DevOps alert rules

All rules inherit the alert settings from index.js.

Provision Rules

To add these alert rules to your account via the CLI, you will need to install the JupiterOne CLI from npm or download source from github:

Install J1 CLI

npm install @jupiterone/jupiterone-client-nodejs -g

Provision Rule Pack

j1 -a <j1AccountId> -u <j1Username> -o provision-alert-rule-pack --alert -f aws-config

Contribution

This repo is coupled to the @jupiterone/jupiterone-alert-rules npm package via Github Workflows.

In order to publish your changes into a new npm package version, your last commit must be the commit that is automatically made via running npm version patch or yarn version --patch. You must then push your changes along with the version tag by using git push --follow-tags.

Doing both of these things will inform the CI to publish a new package version when the edits are merged into main.