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

Revert " DomainTools Iris - Risky DNS Responder" #609

Closed

Conversation

jeromeleonard
Copy link
Contributor

Reverts #587. It looks for specific short report in the observable to add a specific tag. Could you please describe the use-case or the need to do that ?

…on risk score tag from DomainTools. (#587)"

This reverts commit 9e12508.
@jeromeleonard jeromeleonard added the scope:responder Issues/PRs pertaining to responders label Feb 9, 2020
jeromeleonard added a commit that referenced this pull request Feb 9, 2020
@ChuckWoodraska
Copy link
Contributor

DomainTools customers would use this to easily tag a case and artifact based off the DomainTools Iris Risk Score data set.

@EngageCloud
Copy link

@nadouani similar to the first responder.

Lmk. With these merged, we can launch the integration in March

@EngageCloud
Copy link

@nadouani a kind followup on this. Please lmk if anything is needed from our end.

@jeromeleonard jeromeleonard self-assigned this Mar 7, 2020
@jeromeleonard jeromeleonard requested a review from nadouani March 7, 2020 07:06
@jeromeleonard jeromeleonard added this to the 2.6.0 milestone Mar 7, 2020
@jeromeleonard jeromeleonard changed the base branch from develop to release/2.6.0 March 10, 2020 09:42
@jeromeleonard jeromeleonard requested review from a team and removed request for nadouani March 10, 2020 09:42
@jeromeleonard
Copy link
Contributor Author

code added for 2.6.0

@dadokkio dadokkio deleted the revert-587-DT-addriskydnstag_responder branch February 26, 2021 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:new-responder scope:responder Issues/PRs pertaining to responders
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants