-
Notifications
You must be signed in to change notification settings - Fork 236
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
Automated response via Cortex #110
Comments
To-om
added a commit
that referenced
this issue
Jun 29, 2018
To-om
added a commit
that referenced
this issue
Jul 9, 2018
nadouani
added a commit
that referenced
this issue
Jul 9, 2018
nadouani
added a commit
that referenced
this issue
Jul 9, 2018
To-om
added a commit
that referenced
this issue
Jul 10, 2018
nadouani
added a commit
that referenced
this issue
Jul 10, 2018
nadouani
added a commit
that referenced
this issue
Jul 11, 2018
To-om
added a commit
that referenced
this issue
Jul 11, 2018
nadouani
added a commit
that referenced
this issue
Jul 19, 2018
To-om
added a commit
that referenced
this issue
Jul 23, 2018
To-om
added a commit
that referenced
this issue
Jul 23, 2018
To-om
added a commit
that referenced
this issue
Jul 26, 2018
To-om
added a commit
that referenced
this issue
Jul 26, 2018
To-om
added a commit
that referenced
this issue
Jul 26, 2018
To-om
added a commit
that referenced
this issue
Jul 26, 2018
nadouani
added a commit
that referenced
this issue
Jul 26, 2018
To-om
added a commit
that referenced
this issue
Jul 27, 2018
To-om
added a commit
that referenced
this issue
Jul 31, 2018
To-om
added a commit
that referenced
this issue
Jul 31, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Request Type
Feature Request
Work Environment
N/A
Problem Description
I wonder, if it possible to use concept of cortex for response actions.
For example, lock account or enforce password change in AD, blacklist sender in Exchange.
In general, the idea is similar run python script with additional parameters like username or sender domain.
Steps to Reproduce
N/A
Possible Solutions
Complementary information
The text was updated successfully, but these errors were encountered: