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

[SIEMINT-136] DDS: Cisco Secure Web Appliance Integration v1.0.0 #18717

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

madhavpandya-crest
Copy link
Contributor

What does this PR do?

PR for a new integration Cisco Secure Web Appliance 1.0.0

Additional Notes

-- OOTB detection rules JSON would be shared separately with the required teams as a part of separate repository .
-- Since during the standard attribute remapping we are not preserving the source attributes as per suggested best practices, it would result in filters using these standard attributes populating the values of other integrations as well as per current datadog behavior.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Changelog entries must be created for modifications to shipped code
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@neko-dd
Copy link
Contributor

neko-dd commented Sep 30, 2024

Created a ticket for the Docs team to review.

@dj0well dj0well changed the title DDS: Cisco Secure Web Appliance Integration v1.0.0 [SIEMINT-136] DDS: Cisco Secure Web Appliance Integration v1.0.0 Oct 2, 2024
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
Comment on lines 178 to 184
Since Datadog expects all the logs in GMT timezone by default, if the time zone of your Cisco Secure Web Appliance logs is other than GMT, please change it to GMT. Here are the steps:
1. Go to System Administration->Time Zone.
2. Click on `Edit Settings`.
3. Select GMT Offset as the region.
4. Select GMT as the Country.
5. Select GMT (GMT) as the time zone.
6. Submit and commit the changes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Since Datadog expects all the logs in GMT timezone by default, if the time zone of your Cisco Secure Web Appliance logs is other than GMT, please change it to GMT. Here are the steps:
1. Go to System Administration->Time Zone.
2. Click on `Edit Settings`.
3. Select GMT Offset as the region.
4. Select GMT as the Country.
5. Select GMT (GMT) as the time zone.
6. Submit and commit the changes.
Datadog expects all the logs in GMT time zone by default. If the time zone of your Cisco Secure Web Appliance logs is not GMT, please change it to GMT. Here are the steps:
1. Go to **System Administration**, and then **Time Zone**.
2. Click on **Edit Settings**.
3. Select **GMT Offset** as the region.
4. Select **GMT** as the country.
5. Select **GMT (GMT)** as the time zone.
6. Submit and commit the changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated as per the suggestion.

cisco_secure_web_appliance/README.md Outdated Show resolved Hide resolved
@madhavpandya-crest
Copy link
Contributor Author

We have set the version to 7.58.0. If this is intended for any future release, please let us know, as an update will be necessary for this PR. Thank you!

michaelcretzman
michaelcretzman previously approved these changes Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants