Skip to main content

AppOmni

AppOmni is a SaaS Security Posture Management (SSPM) platform that monitors and secures SaaS applications. You can bring application, violation, violation definition, person, and team data from AppOmni into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with AppOmni and how to obtain that information from AppOmni. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select AppOmni from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate AppOmni with Brinqa:

  • API URL: The AppOmni API base URL. The default is https://app.appomni.com/api/v1.
  • API Token: The API token for authenticating with the AppOmni API.

The connector authenticates using an API token. All API requests include the token in the Authorization header as Token <api_token>. The API token is generated from the AppOmni platform under Settings → API.

Additional settings

The AppOmni connector contains additional options for specific configuration:

  • Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
  • Parallel requests: The maximum number of parallel API requests. The default setting is 8.
  • Maximum retries: The maximum number of times that the integration attempts to connect to the AppOmni API before giving up and reporting a failure. The default setting is 5.

Types of data to retrieve

The AppOmni connector can retrieve the following types of data from the AppOmni API:

Table 1: Data retrieved from AppOmni

Connector ObjectRequiredMaps to Data Model
AppOmniGroupYesTeam
AppOmniUserYesPerson
MonitoredServiceYesApplication
PostureFindingYesViolation
PostureFindingDefinitionYesViolation Definition
info

For detailed steps on how to view the data retrieved from AppOmni in the Brinqa Platform, see How to view your data.

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes.

AppOmniGroup

Table 2: AppOmniGroup attribute mappings

Source Field NameSDM Attribute
Generated (set to "Team")CATEGORIES
displayNameDESCRIPTION
Generated (sync capture timestamp)LAST_CAPTURED
members[*].valueMEMBERS
Generated (computed from members array size)MEMBER_COUNT
displayNameNAME
meta.createdSOURCE_CREATED_DATE
meta.lastModifiedSOURCE_LAST_MODIFIED
Generated (set to "active")STATUS
idUID
AppOmniUser

Table 3: AppOmniUser attribute mappings

Source Field NameSDM Attribute
Generated (set to "Person")CATEGORIES
Enterprise extension departmentDEPARTMENT
displayNameDESCRIPTION
Primary email from emailsEMAIL
emails[*].valueEMAILS
active (active/inactive)EMPLOYMENT_STATUS
name.givenNameFIRST_NAME
groups[*].valueGROUPS
titleJOB_TITLE
Generated (sync capture timestamp)LAST_CAPTURED
name.familyNameLAST_NAME
displayNameNAME
meta.createdSOURCE_CREATED_DATE
meta.lastModifiedSOURCE_LAST_MODIFIED
active (active/inactive)STATUS
idUID
userNameUSERNAME
MonitoredService

Table 4: MonitoredService attribute mappings

Source Field NameSDM Attribute
Generated ("Application" + serviceType)CATEGORIES
MonitoredServiceResource.descriptionDESCRIPTION
MonitoredServiceResource.enforcementModeENFORCEMENT_MODE
MonitoredServiceResource.externalIdEXTERNAL_ID
MonitoredServiceResource.integrationConnectedINTEGRATION_CONNECTED
MonitoredServiceResource.isArchivedIS_ARCHIVED
Generated (sync capture timestamp)LAST_CAPTURED
MonitoredServiceResource.name or serviceNameNAME
MonitoredServiceResource.openIssuesCountOPEN_ISSUES_COUNT
MonitoredServiceResource.scoreSCORE
MonitoredServiceResource.serviceIdSERVICE_ID
MonitoredServiceResource.serviceNameSERVICE_NAME
MonitoredServiceResource.serviceTypeSERVICE_TYPE
MonitoredServiceResource.createdSOURCE_CREATED_DATE
MonitoredServiceResource.modifiedSOURCE_LAST_MODIFIED
Generated (derived from isArchived / enforcementMode)STATUS
MonitoredServiceResource.idUID
PostureFinding

Table 5: PostureFinding attribute mappings

Source Field NameSDM Attribute
FindingResource.assigneeASSIGNEE
FindingResource.description or summaryDESCRIPTION
FindingResource.findingTypeFINDING_TYPE
FindingResource.firstOpenedFIRST_OPENED
FindingResource.lastClosedLAST_CLOSED
Generated (sync capture timestamp)LAST_CAPTURED
FindingResource.lastOpenedLAST_OPENED
FindingResource.monitoredServiceMONITORED_SERVICE
FindingResource.titleNAME
FindingResource.policyIdPOLICY_ID
FindingResource.policyNamePOLICY_NAME
FindingResource.statusPROVIDER_STATUS
FindingResource.remediationStepsREMEDIATION_STEPS
FindingResource.appomniRiskLevelRISK_LEVEL
FindingResource.appomniRiskScoreRISK_SCORE
FindingResource.severity or appomniRiskLevel (normalized)SEVERITY
FindingResource.createdSOURCE_CREATED_DATE
FindingResource.modifiedSOURCE_LAST_MODIFIED
FindingResource.status (normalized)SOURCE_STATUS
FindingResource.summarySUMMARY
FindingResource.monitoredServiceTARGETS
FindingResource.policyIdTYPE
FindingResource.idUID
PostureFindingDefinition

Table 6: PostureFindingDefinition attribute mappings

Source Field NameSDM Attribute
PolicyResource.categoryCATEGORIES
PolicyResource.categoryCATEGORY
PolicyResource.descriptionDESCRIPTION
PolicyResource.externalIdEXTERNAL_ID
PolicyResource.isReferenceIS_REFERENCE
Generated (sync capture timestamp)LAST_CAPTURED
PolicyResource.nameNAME
PolicyResource.policyFrameworkPOLICY_FRAMEWORK
PolicyResource.policyTypePOLICY_TYPE
PolicyResource.severity (normalized)SEVERITY
Computed from normalized severitySEVERITY_SCORE
PolicyResource.createdSOURCE_CREATED_DATE
PolicyResource.modifiedSOURCE_LAST_MODIFIED
PolicyResource.severity (raw)SOURCE_SEVERITY
PolicyResource.policyTypeTAGS
PolicyResource.idUID

Operation options

The AppOmni connector supports the following operation options. See connector operation options for information about how to apply them.

MonitoredService

Table 7: MonitoredService operation options

Connector ObjectOptionAll Possible ValuesDescriptionExample
MonitoredServiceannotationsAny stringInclude computed fields like open_issues_count. Default is 1.Key: annotations Value: 1. Includes computed annotations in the response.
enforcementModeAny stringFilter by enforcement mode.Key: enforcementMode Value: monitoring. Only retrieves monitored services in monitoring mode.
isArchivedtrue, falseFilter by archived status.Key: isArchived Value: false. Excludes archived services.
serviceTypeAny stringFilter by service type.Key: serviceType Value: salesforce. Only retrieves Salesforce monitored services.
PostureFinding

Table 8: PostureFinding operation options

Connector ObjectOptionAll Possible ValuesDescriptionExample
PostureFindingmonitoredServiceInAny stringComma-separated monitored service IDs to filter by.Key: monitoredServiceIn Value: 123,456. Only retrieves findings for the specified services.
riskScoreGteAny stringMinimum risk score threshold.Key: riskScoreGte Value: 5. Only retrieves findings with a risk score of 5 or higher.
riskScoreLteAny stringMaximum risk score threshold.Key: riskScoreLte Value: 8. Only retrieves findings with a risk score of 8 or lower.
sourceTypeAny stringFilter by source type.Key: sourceType Value: scanner. Only retrieves scanner-sourced findings.
statusopen, closedFilter by finding status.Key: status Value: open. Only retrieves open findings.
PostureFindingDefinition

Table 9: PostureFindingDefinition operation options

Connector ObjectOptionAll Possible ValuesDescriptionExample
PostureFindingDefinitionisReferencetrue, falseFilter by reference policies.Key: isReference Value: true. Only retrieves reference/system policies.

APIs

The AppOmni connector uses the AppOmni API. Specifically, it uses the following endpoints:

Table 10: AppOmni API endpoints

Connector ObjectAPI Endpoint
AppOmniGroupGET /scim/v2/Groups
AppOmniUserGET /scim/v2/Users
MonitoredServiceGET /core/monitoredservice/
PostureFindingGET /findings/finding/
PostureFindingDefinitionGET /core/policy/

Changelog

The AppOmni connector has undergone the following changes:

Table 11: AppOmni connector changelog

VersionDescriptionDate Published
3.0.0Initial Integration+ release.TBD