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

[Bug] Investigate Analyzer Broken #703

Closed
jaredstewart101 opened this issue Feb 21, 2020 · 3 comments
Closed

[Bug] Investigate Analyzer Broken #703

jaredstewart101 opened this issue Feb 21, 2020 · 3 comments
Assignees
Labels
category:bug Issue is related to a bug
Milestone

Comments

@jaredstewart101
Copy link

Describe the bug
I've configured the investigate analyzer with our API key from Cisco subscription, but when I attempt to run the analyzer using the "Categorization" feature, it returns with a message saying:

"Unknown Investigate service or invalid data type"

To Reproduce
Steps to reproduce the behavior:

  1. Configure analyzer with API key from Cisco Umbrella
  2. Add domain observable to case such as "amazon.com"
  3. Run "Investigate_Categorization_1_0"
  4. Report will fail with message "Unknown Investigate service or invalid data type"

Expected behavior
What should happen is a report should be returned with the categorization of the domain such as "Safe", "Suspicious", or "Malicious".

Complementary information
Screenshot of error message received after running analyzer on "www.amazon.com"
Screen Shot 2020-02-21 at 12 01 53 PM

Work environment

  • Client OS: Docker
  • Server OS: Ubuntu 16.04
  • Browse type and version: Chrome
  • Cortex version: 3.0.0-1
  • Cortex Analyzer/Responder name: Investigate
  • Cortex Analyzer/Responder version: 1.0

Possible solutions
It almost seems that since this analyzer was written, the API for Investigate has changed and the new analyzer doesn't work with it.

@jaredstewart101 jaredstewart101 added the category:bug Issue is related to a bug label Feb 21, 2020
@jaredstewart101
Copy link
Author

I just saw that this bug was fixed in Cortex 2.5 I believe. The docker image for Cortex 3.0.0 needs to be updated with the fix. I removed the following code from the investigate_analyzer.py file and it works now:
else: self.error('Unknown Investigate service or invalid data type')

That was mentioned in this commit: 19164d7

@jeromeleonard jeromeleonard added this to the 2.6.0 milestone Feb 28, 2020
@garanews
Copy link
Contributor

Fixed in 2.6.0 with #718

@jeromeleonard
Copy link
Contributor

@jaredstewart101 finally we reverted the version bump. I tested on the version fixed with Cortex-Analyzers 2.5.0 and docker image and it works very well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bug Issue is related to a bug
Projects
None yet
Development

No branches or pull requests

3 participants