Add Silverfort Identity Security integration

[FrankGasparovic]

Description

Please provide a detailed description of your changes. This helps reviewers understand your work and its context.

What problem does this PR solve?

This PR adds a new community integration for Silverfort Identity Security, enabling Google SecOps SOAR users to interact with Silverfort's identity protection platform. The integration provides capabilities for:

• Risk Management: Get and update entity risk scores for users and resources
• Service Account Protection: List, retrieve, and configure protection policies for service accounts
• Authentication Policy Management: Create, update, enable/disable authentication policies

How does this PR solve the problem?

Added a complete integration under content/response_integrations/third_party/community/silverfort/ with:

• 11 Actions:

  • Ping - Test connectivity to Silverfort API
  • Get Entity Risk - Retrieve risk information for users/resources
  • Update Entity Risk - Set risk levels based on external threat intelligence
  • Get Service Account - Get detailed service account information
  • List Service Accounts - List all service accounts with pagination
  • Update SA Policy - Configure service account protection policies
  • Get Policy - Retrieve authentication policy details
  • List Policies - List all authentication policies
  • Update Policy - Modify policy settings
  • Change Policy State - Enable/disable policies

• Core Components:

  • JWT-based authentication with automatic token refresh
  • Separate API clients for Risk, Service Account, and Policy APIs
  • Comprehensive data models using Python dataclasses
  • Custom exception handling

• Tests:

  • 16 unit tests covering all actions
  • Mock infrastructure for API responses
  • Standard import test (test_defaults/test_imports.py)

Any other relevant information (e.g., design choices, tradeoffs, known issues):

• The integration supports multiple API credentials (Risk API, Service Accounts API, Policies API) configured separately in the integration settings
• Uses slots=True for dataclasses for memory efficiency
• All tests pass and validation completes successfully
• Follows the same patterns as other community integrations (e.g., grey_noise, vectra_rux)

---

Checklist:

Please ensure you have completed the following items before submitting your PR.
This helps us review your contribution faster and more efficiently.

General Checks:

• I have read and followed the project's contributing.md guide.
• My code follows the project's coding style guidelines.
• I have performed a self-review of my own code.
• My changes do not introduce any new warnings.
• My changes pass all existing tests.
• I have added new tests where appropriate to cover my changes. (If applicable)
• I have updated the documentation where necessary (e.g., README, API docs). (If applicable)

Open-Source Specific Checks:

• My changes do not introduce any Personally Identifiable Information (PII) or sensitive customer data.
• My changes do not expose any internal-only code examples, configurations, or URLs.
• All code examples, comments, and messages are generic and suitable for a public repository.
• I understand that any internal context or sensitive details related to this work are handled separately in internal systems (Buganizer for Google team members).

For Google Team Members and Reviewers Only:

• I have included the Buganizer ID in the PR title or description (e.g., "Internal Buganizer ID: 123456789" or "Related Buganizer: go/buganizer/123456789").
• I have ensured that all internal discussions and PII related to this work remain in Buganizer.
• I have tagged the PR with one or more labels that reflect the pull request purpose.

---

Screenshots (If Applicable)

N/A - Backend integration only, no UI changes.

---

Further Comments / Questions

• Validation Results: All 16 tests pass, mp validate --integration silverfort completes successfully
• Build Output: Integration builds correctly with mp build --integration silverfort
• Dependencies: Uses standard dependencies (requests, PyJWT) already available in the SOAR environment

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[AmitJ98]

Hi @FrankGasparovic , my name in Amit i will review your pr.
I see that you did not sign the google cla, please do so as mentioned here: https://github.com/chronicle/content-hub/blob/main/docs/contributing.md.
and secondly please resolve all the comments.
If you need any help or have issues feel free to contact me.

[FrankGasparovic]

Hi @FrankGasparovic , my name in Amit i will review your pr. I see that you did not sign the google cla, please do so as mentioned here: https://github.com/chronicle/content-hub/blob/main/docs/contributing.md. and secondly please resolve all the comments. If you need any help or have issues feel free to contact me.

Thanks so much Amit. We are just waiting on the Silverfort legal team approval on the CLA, hoping I have that executed on Monday or Tuesday. I've also addressed all your comments. Please let me know if there are any other issues I can sort out.

[AmitJ98]

Hi @FrankGasparovic , my name in Amit i will review your pr. I see that you did not sign the google cla, please do so as mentioned here: https://github.com/chronicle/content-hub/blob/main/docs/contributing.md. and secondly please resolve all the comments. If you need any help or have issues feel free to contact me.

Thanks so much Amit. We are just waiting on the Silverfort legal team approval on the CLA, hoping I have that executed on Monday or Tuesday. I've also addressed all your comments. Please let me know if there are any other issues I can sort out.

The last thing you need to do is to make sure linter check are passing.
from your cli (when you are in the integration dir) run mp check . and mp format . and make sure the checks are passing without any errors.

[FrankGasparovic]

Hi @FrankGasparovic , my name in Amit i will review your pr. I see that you did not sign the google cla, please do so as mentioned here: https://github.com/chronicle/content-hub/blob/main/docs/contributing.md. and secondly please resolve all the comments. If you need any help or have issues feel free to contact me.

Thanks so much Amit. We are just waiting on the Silverfort legal team approval on the CLA, hoping I have that executed on Monday or Tuesday. I've also addressed all your comments. Please let me know if there are any other issues I can sort out.

The last thing you need to do is to make sure linter check are passing. from your cli (when you are in the integration dir) run mp check . and mp format . and make sure the checks are passing without any errors.

Thanks Amit, validated both commands and fixed the issues that resulted. Will get the CLA executed ASAP and hopefully we can get this merged this week.