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

Netskope CCP Integration #11777

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

Conversation

mitchellgulledge2
Copy link

Required items, please complete

Change(s):

  • Added Netskope CCP data connector to existing solution

Reason for Change(s):

  • GA for Netskope CCP Integration

Testing Completed:

  • Netskope Validated in Internal MSFT environment

@mitchellgulledge2 mitchellgulledge2 requested review from a team as code owners February 7, 2025 18:11
@v-prasadboke v-prasadboke self-assigned this Feb 10, 2025
@v-prasadboke v-prasadboke added Connector Connector specialty review needed Solution Solution specialty review needed labels Feb 10, 2025
@mitchellgulledge2
Copy link
Author

@v-prasadboke let me know if any other changes need to be made and thanks in advance

@v-prasadboke
Copy link
Contributor

Hello @mitchellgulledge2, i have made some required changes.
Can you share demo credentials to test connector.

you can share it over mail or teams.
my handle : [email protected]

@v-prasadboke
Copy link
Contributor

Hello @mitchellgulledge2, Please try to deploy and test the connector using the maintemplate i commited.

it is throwing me 409 error

@mitchellgulledge2
Copy link
Author

The 409 is because we were running too many deployments with the same apikey on the same tenant for the same endpoint. Data should be flowing correctly but we discovered a few issues.

  1. With some of the sample data sets Sentinel converts integer data types to type 32. Some of our data sets for like incident ID are 64 bit.
  2. When we converted data type from int to long we noticed that after the 16th digit in the integer that Sentinel converts anything after to 0. So customers reported incorrected Incident IDs since it appears sentinel does a javascript evaluation (didnt see this documented anywhere)
    So now we are having to test to try and see if converting to string resolves issue but we should likely document that sentinel cannot support anything past a long value of 9007199254740991.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed Solution Solution specialty review needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants