FireEye ETP - PAPP-20333 - FIPS compliance for FireEye ETP

[brian-phantom]

Please ensure your pull request (PR) adheres to the following guidelines:

• Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist

Please check if your PR fulfills the following requirements:

• [x] Testing of all the changes has been performed (for bug fixes / features)
• [x] The readme.html and readme.md have been reviewed and added / updated if needed (for bug fixes / features)
• [x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
• [x] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
• [x] Verify all checks are passing.
• [x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
• [x] Do NOT submit updates to dependencies unless it fixes an issue.
• [x] Limit your pull request to one application and submit multiple pull requests if necessary.

  Pull Request Type

Please check the type of change your PR introduces:

• [ ] New App
• [x] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Documentation
• [ ] Other (please describe):

Release Notes (REQUIRED)

Use sha-256 instead of MD5 for FIPS compliance.

[splunk-soar-connectors-bot]

Hello!

The apps in this repo have been migrated to our new GitHub org https://github.com/splunk-soar-connectors under separate repositories. Kindly re-submit your PR to the repo in the new org for the app you are contributing to.