Skip to content

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

Open
wants to merge 31 commits into
base: contrib/seanmacdonald8_Darktrace-Email-1
Choose a base branch
from

Conversation

seanmacdonald8
Copy link
Contributor

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

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

fixes: link to the issue

Description

Creating a new integration with Darktrace/EMAIL as part of the existing Darktrace pack.

Must have

  • Tests
  • Documentation

@CLAassistant
Copy link

CLAassistant commented Apr 10, 2025

CLA assistant check
All committers have signed the CLA.

@content-bot content-bot added Contribution Thank you! Contributions are always welcome! External PR Partner Support Level Indicates that the contribution is for Partner supported pack labels Apr 10, 2025
@content-bot content-bot changed the base branch from master to contrib/seanmacdonald8_Darktrace-Email-1 April 10, 2025 23:58
@content-bot
Copy link
Collaborator

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.
For your convenience, here is a link to the contributions SLAs document.

@content-bot
Copy link
Collaborator

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.

@content-bot
Copy link
Collaborator

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)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sensitive data (id)
is used in a hashing algorithm (SHA1) that is insecure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contribution Form Filled Whether contribution form filled or not. Contribution Thank you! Contributions are always welcome! External PR Partner Support Level Indicates that the contribution is for Partner supported pack Partner Partner-Approved Security Review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants