In order to migrate from URL list to Destination profiles, I need the Destinations API to support deduping values the way the current URL API does when you append values to a list.
If I call the URL endpoint: /api/v2/policy/urllist/{id}/append
And add the same site, example ....www.bad.com. The api automatically dupes the entry and only adds it if it doesn't exist. This is helpful because some of our URL list are automated via threat intel feeds. While we try to dedup the IOCs before updating the URL list, some do get through, but the URL api handles it.
But with destination profiles, if you call /api/v2/profiles/destinations{id}/values and your payload is to append. Example:
{
"details": false,
"interactive": true,
"operation": {
"op": "append",
"values": [
"www.bad.com"
]
}
}
It doesn't dedup and just continues to add to the list.
So, may I missing something? Is there some query parameter or destination profile api endpoint I should be calling to dedup? Or do I need to submit a feature request somewhere for the API to handle this?
My concerns are:
- I don’t want duplicates to be counted against our tenant limit
- multiple entries increases the difficulty of an analyst troubleshooting an issue
I have read both of these articles, but didn’t see anything mentioned about appending to profiles or deduplication.
https://support.netskope.com/s/article/Destination-Profiles-Configuration-Guide?_gl=110j6qkggaNjM2ODExMDc0LjE3NzI4MjM0MTA.ga_NP0SZ0PW1M*czE3NzY4NjUyNTIkbzExJGcxJHQxNzc2ODY1Mjg2JGoyNiRsMCRoMA..
https://support.netskope.com/s/article/URL-Lists-to-Destination-Profiles-Migration?_gl=110j6qkggaNjM2ODExMDc0LjE3NzI4MjM0MTA.ga_NP0SZ0PW1M*czE3NzY4NjUyNTIkbzExJGcxJHQxNzc2ODY1Mjg2JGoyNiRsMCRoMA..
