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.

Sign up for GitHub

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

Jump to bottom

Feature: Crowdsource Plugin #3

Closed
ghost opened this issue Jan 30, 2017 · 1 comment
Closed

Feature: Crowdsource Plugin #3

ghost opened this issue Jan 30, 2017 · 1 comment
Assignees
@jacknagz
Labels
alerting outputs feature request roadmap

Comments

@ghost
Copy link

ghost commented Jan 30, 2017 •
edited by ghost

Target: Q1/Q2'17

The idea of crowdsourcing your alerts isn't new. Slack does this and the blog speaks at length to the benefits. In the near future, StreamAlert will support this use-case, allowing you to decentralize your triage efforts, getting alerts to those with the most context. We’re aiming for Q1/Q2'17.
@ghost ghost assigned jacknagz Jan 30, 2017
@ghost ghost changed the title Crowdsource Plugin Feature: Crowdsource Plugin Jan 30, 2017
ryandeivert added a commit that referenced this issue Apr 10, 2017
@ryandeivert
# This is a combination of 9 commits.
0c520d0 
# This is the 1st commit message:
[lambda][output] output processor modular updates

# This is the commit message #2:

[cli] restricting colon characters along with spaces in user input for service descriptors

# This is the commit message #3:

[cli] migrating some code from the runner to the new outputs file for the cli

# This is the commit message #4:

[rules][testing] updating rules to conform to new outputs configuration style. also updating tests to go with this change

# This is the commit message #5:

[lambda][alert] remove encrypted_credentials folder

# This is the commit message #6:

[tf] fix bug in streamalert.secrets iam policy

# This is the commit message #7:

[lambda][rule] send a single alert to SNS without wrapping in a list

# This is the commit message #8:

[lambda] bug fixes: make it work

* load the outputs.json config
* package in the conf directory
* load the conf
* read s3 buckets from the conf
* fix bugs in request helper
* more

# This is the commit message #9:

[lambda][output] masking slack url during input and restricting the use of colons (:) in unmasked input
@ghost
Copy link
Author

ghost commented Sep 20, 2017

StreamAlert supports sending alerts, on a per-rule basis, to any defined Slack or PagerDuty outputs. Closing out

@ghost ghost closed this as completed Sep 20, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacknagz jacknagz

Labels
alerting outputs feature request roadmap
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacknagz