Discovery capabilities of custom integrations
Single Sign-On & CASB System
Service discovery
- Used to discover new SaaS and add the services to your workspace
- Data types used: Application
- Required data:
appID
string (max 255) - unique identifier of the app in the data sourceappName
string (max 255) - display- or clearname of the app in the data source
Examples
AzureAD
Importing Applications from GET <https://graph.microsoft.com/v1.0/applications
>
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#applications",
"value": [
{
"appId": "00000000-0000-0000-0000-000000000000",
"identifierUris": [ "http://contoso/" ],
"displayName": "My app",
"publisherDomain": "contoso.com",
"signInAudience": "AzureADMyOrg"
}
]
}
Map appId
to appID
and displayName
to appName
and ingest data into your ADX database.
Service and user account discovery (support planned)
- Used to discover new SaaS and add the services to your workspace
- Data types used: Application, User
- Required data:
appID
string (max 255) - unique identifier of the app in the data sourceappName
string (max 255) - display- or clearname of the app in the data sourcename
string (max 64) - full or display name of the useremail
string (max 255) - user's email addresslastSeen
string (ISO 8601) - time of the login or usage event
Examples
Netskope
Importing application events from POST https://<tenant-name>.goskope.com/api/v1/events?type=application
{
"status": "success",
"data": [
{
"nsdeviceuid": "00000000-0000-0000-0000-000000000000",
"src_geoip_src": 2,
"src_region": "California",
"app": "Syncplicity",
"appcategory": "Cloud Storage",
"activity": "View All",
"timestamp": 1575159388,
"user": "[email protected]",
"userkey": "[email protected]",
"user_name": "john smith",
"device": "Windows Device",
...
}
]
}
Mapping:
app
→appName
- there is no direct equivalent for
appID
. in this case, we recommend usingapp
or generating it by creating an md5 hash ofapp
user_name
→name
user
oruserkey
→email
timestamp
→lastSeen
Financial System
Service discovery
- Used to discover new SaaS and add the services to your workspace
- Data types used: Vendor
- Required data:
vendorID
string (max 255) - unique identifier of the vendor in the data sourcevendorName
string (max 255) - display- or clearname of the vendor in the data source
Service and spend discovery
- Used to discover new SaaS and Invoices and add them to your workspace
- Data types used: Vendor, Invoice
- Required data:
vendorID
string (max 255) - unique identifier of the vendor in the data sourcevendorName
string (max 255) - display- or clearname of the vendor in the data sourceinvoiceID
string (max 255) - unique identifier of the invoice in the data sourcedescription
string (max 255) - description of the invoice in the data sourceamount
decimal - the total amount of the invoice in the data source- example of valid amount:
12345.68
- 0 is not a valid amount
- example of valid amount:
currency
string (ISO 4217) - the currency of the invoice in the data source- example of valid currency format:
USD
,EUR
- example of valid currency format:
invoiceDate
string (ISO 8601) - date of the invoice in the data source- example of valid invoiceDate format:
2020-11-03T00:00:00Z
- example of valid invoiceDate format:
Contract Management System
Service discovery (early access)
- Used to discover new SaaS and add the services to your workspace
- Data types used: Supplier
- Required data:
supplierExternalID
string (max 255) - unique identifier of the vendor in the data sourcesupplierName
string (max 255) - display- or clearname of the vendor in the data source
Service and contracts discovery (early access)
- Used to discover new SaaS and Contracts and add them to your workspace
- Data types used: Supplier, Contract
- Required data:
externalID
string (max 255) - unique identifier of the contract in the data sourcesupplierExternalID
string (max 255) - unique identifier of the vendor in the data sourcesupplierName
string (max 255) - display- or clearname of the vendor in the data sourcetype
- eitherregular
orsubscription
startDate
string (ISO 8601) - start date of the contract in the data source- example of valid startDate format:
2020-11-03T00:00:00Z
- example of valid startDate format:
endDate
string (ISO 8601) - end date of the contract in the data source- example of valid endDate format:
2020-11-03T00:00:00Z
- example of valid endDate format:
renewalType
- eitherautomatic
ormanual
totalValue
decimal - total value of the contract- example of valid amount:
12345.68
- example of valid amount:
currency
string (ISO 4217) - the currency of the invoice in the data source- example of valid currency format:
USD
,EUR
- example of valid currency format:
- Optional data:
contractTitle
string (max 255) - descriptive contract titlevolume
integer - volume of the contractdescription
string (max 255) - custom description of the contract
Expense Management System
Spend discovery (support planned)
Credit Card
Spend discovery (support planned)
HR Information System
People discovery (support planned)
Departments discovery (support planned)
People and departments discovery (support planned)
Updated 4 months ago