Add support for API 2.0 in Mimecast Event Collector

[kamalq97]

Related Issues

fixes: CIAC-14914

Description

Add support for Mimecast API 2.0 and implement async event fetching logic.

Version release notes:

• Breaking Change: Migrated from the legacy API 1.0 authentication method to OAuth2 client credentials flow for Mimecast API 2.0 following the announcement about Mimecast API 1.0 End of Life.

  • Added support for new API 2.0 authentication using Client ID and Client Secret parameters.
  • Deprecated support for API 1.0 authentication and removed the Application ID, Application Key, Access Key, and Secret Key parameters.

• Breaking Change: Restricted the First fetch timestamp parameter to audit events due to SIEM API endpoint limitations.

• Added support for the Fetch event types parameter which specifies the types of events to fetch.

• Added support for the event_types, start_date, and end_date arguments in the mimecast-get-events command.

• Updated the Docker image to: demisto/py3-tools:1.0.0.6308650.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
Packs/Mimecast/Integrations/MimecastEventCollector
MimecastEventCollector.py	417	66	84%	126–127, 147, 163–164, 173, 252–253, 256–258, 260–263, 266–270, 274–275, 279, 283, 286, 357, 433, 437–438, 533, 607, 622, 626, 700–701, 785–790, 794–796, 798, 807–809, 812–813, 816–817, 819, 823, 899–900, 902–904, 906–908, 911–912, 914, 961
TOTAL	417	66	84%

Tests	Skipped	Failures	Errors	Time
30	0 💤	0 ❌	0 🔥	8.700s ⏱️

[content-bot]

🤖 Content-bot Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

[content-bot]

Hi there! Thanks for the update to the Mimecast pack. I've reviewed the changes and have a few points to discuss, primarily regarding the proxy implementation and test mocking.

Please ensure proxy arguments are passed correctly to the request methods rather than the aiohttp session, and update the unit tests to use AsyncMock for asynchronous methods. It would also be helpful to clarify the API 2.0 credential steps in the documentation and consolidate the breaking changes in the release notes.

Great work so far

@richardbluestone, @JasBeilin please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

[richardbluestone]

Hi there! Thanks for the update to the Mimecast pack. I've reviewed the changes and have a few points to discuss, primarily regarding the proxy implementation and test mocking.

Please ensure proxy arguments are passed correctly to the request methods rather than the aiohttp session, and update the unit tests to use AsyncMock for asynchronous methods. It would also be helpful to clarify the API 2.0 credential steps in the documentation and consolidate the breaking changes in the release notes.

Great work so far

@richardbluestone, @JasBeilin please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

@julieschwartz18 Can you do this?

[julieschwartz18]

@kamalq97 Doc review complete. Please confirm the suggested edits and regenerate the integration README from the YAML file. In the meantime, adding the label docs-approved.

[content-bot]

Validate summary
The following errors were thrown as a part of this pr: BC112.
The following errors cannot be ignored: BC112.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: BC112.

Verdict: PR can be force merged from validate perspective? ✅