-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Darktrace email 1 #39551
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
base: contrib/seanmacdonald8_Darktrace-Email-1
Are you sure you want to change the base?
Darktrace email 1 #39551
Conversation
Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @MosheEichler will know the proposed changes are ready to be reviewed. |
Unfortunately, your PR review will be slightly delayed because of an Israeli holiday in the upcoming week (the 12th of April - the 19th of April). Thank you in advance for your patience and understanding. |
Hi @seanmacdonald8, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link. |
|
||
return hmac.new( | ||
private_token.encode('ASCII'), | ||
f'{query_uri}{query_string}\n{public_token}\n{date}'.encode('ASCII'), |
Check failure
Code scanning / CodeQL
Use of a broken or weak cryptographic hashing algorithm on sensitive data High
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
Sensitive data (id)
…/content into Darktrace-Email-1
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
fixes: link to the issue
Description
Creating a new integration with Darktrace/EMAIL as part of the existing Darktrace pack.
Must have