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

API Keys to be submitted through Cortex for Analyzers #7

Closed
JohnOmernik opened this issue Feb 16, 2017 · 1 comment
Closed

API Keys to be submitted through Cortex for Analyzers #7

JohnOmernik opened this issue Feb 16, 2017 · 1 comment

Comments

@JohnOmernik
Copy link

API Keys to be submitted through Cortex for Analyzers

Request Type

Feature Request

Work Environment

NA

Problem Description

For some systems, having one key for all users doesn't match the terms of service of the endpoint APIs. Thus, it would be nice to have users in say thehive have the ability to specify keys for specific endpoints (Say Passive DNS or Virustotal) in their accounts, and when they request analyzer action, those keys are passed to the cortex, which then uses those keys as the key to the backend.

This would allow better usage tracking. There could be "Default" keys if a user doesn't specify a key to say virus total, it would use the shared key. But if we do that, we should get the ability to enforce per user limits on shared keys for specific services. This would force almost all requests coming from the thehive to cortext to include a user identifier.

@jeromeleonard
Copy link
Contributor

Cortex 2.x provides Organizations and accounts dedicated configuration.thus, this allows different groups to specify their API keys.

To-om pushed a commit that referenced this issue Apr 17, 2019
Onyphe Domain name change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants