Skip to main content

Entro Security

Entro Security is a non-human identity (NHI) security platform that integrates with your security framework to fetch and synchronize security-related data, including accounts, employees, non-human identities, risks, and exposed secrets. You can bring account, employee, NHI token, risk, and exposed secret data from Entro Security 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 Entro Security and how to obtain that information from Entro. 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 Entro Security 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 Entro Security with Brinqa:

  • API URL: The Entro API base URL (e.g., https://<server>/).

  • API key: The API key for authenticating requests to the Entro API.

The connector authenticates using an API key. It includes the API key in all API requests to authorize access to the Entro Security platform.

Additional settings

The Entro Security connector contains additional options for specific configuration:

  • Page size: The maximum number of records to get per API request. The default setting is 50.
  • Parallel requests: The maximum number of parallel API requests for fetching details. The default setting is the minimum of 4 or the number of available CPU cores.
  • Maximum retries: The maximum number of times that the integration attempts to connect to the Entro Security API before giving up and reporting a failure. The default setting is 5.

Types of data to retrieve

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

Table 1: Data retrieved from Entro Security

Connector ObjectRequiredMaps to Data Model
AccountYesCloud Resource
EmployeeYesPerson
Exposed SecretYesAlert
Exposed Secret DefinitionNoAlert Definition
NHI TokenYesN/A
RiskYesViolation
Risk DefinitionNoViolation Definition
info

For detailed steps on how to view the data retrieved from Entro Security 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.

Account

Table 2: Account attribute mappings

Source Field NameSDM Attribute
AccountResource.accountTypeACCOUNT_TYPE
AccountResource.connectorIdCONNECTOR_ID
AccountResource.createdAtCREATED_AT
AccountResource.createdAtSOURCE_CREATED_DATE
AccountResource.environmentENVIRONMENT
AccountResource.statusPROVIDER_STATUS
AccountResource.status (normalized)SOURCE_STATUS
AccountResource.uidACCOUNT_UID
AccountResource.uidNAME
AccountResource.uidUID
Generated (set to "Cloud Resource")CATEGORIES
Generated (sync capture timestamp)LAST_CAPTURED
Employee

Table 3: Employee attribute mappings

Source Field NameSDM Attribute
EmployeeResource.accountsACCOUNTS
EmployeeResource.aliasesALIASES
EmployeeResource.azureEmployeeTypeAZURE_EMPLOYEE_TYPE
EmployeeResource.creationDateCREATION_DATE
EmployeeResource.creationDateSOURCE_CREATED_DATE
EmployeeResource.divisionDIVISION
EmployeeResource.emailEMAILS
EmployeeResource.employeeTypeEMPLOYEE_TYPE
EmployeeResource.fullNameFULL_NAME
EmployeeResource.fullNameNAME
EmployeeResource.idpSourcesIDP_SOURCES
EmployeeResource.lastLoginLAST_LOGIN
EmployeeResource.managerMANAGERS
EmployeeResource.organizationORGANIZATION
EmployeeResource.ownerUidOWNER_UID
EmployeeResource.phonePHONE_NUMBERS
EmployeeResource.statusPROVIDER_STATUS
EmployeeResource.status (normalized)SOURCE_STATUS
EmployeeResource.titleJOB_TITLE
EmployeeResource.titleTITLE
Generated (md5 of email and fullName)UID
Generated (set to "Person", "Identity")CATEGORIES
Generated (sync capture timestamp)LAST_CAPTURED
Exposed Secret

Table 4: Exposed Secret attribute mappings

Source Field NameSDM Attribute
ExposedSecretResource.account.accountIdACCOUNT_ID
ExposedSecretResource.account.accountTypeACCOUNT_TYPE
ExposedSecretResource.account.environmentACCOUNT_ENVIRONMENT
ExposedSecretResource.account.environmentTypeACCOUNT_ENVIRONMENT_TYPE
ExposedSecretResource.account.uidACCOUNT_UID
ExposedSecretResource.account.uidTARGETS
ExposedSecretResource.employee.emailEMPLOYEE_EMAIL
ExposedSecretResource.employee.nameEMPLOYEE_NAME
ExposedSecretResource.exposedIdUID
ExposedSecretResource.exposureTimeEXPOSURE_TIME
ExposedSecretResource.exposureTimeFIRST_FOUND
ExposedSecretResource.hashHASH
ExposedSecretResource.isGenericIS_GENERIC
ExposedSecretResource.isPublicIS_PUBLIC
ExposedSecretResource.keyIdKEY_ID
ExposedSecretResource.locationLOCATION
ExposedSecretResource.locationTypeLOCATION_TYPE
ExposedSecretResource.occurrencesOCCURRENCES
ExposedSecretResource.ownerOWNER
ExposedSecretResource.pathPATH
ExposedSecretResource.redactedSecretREDACTED_SECRET
ExposedSecretResource.scopeSCOPE
ExposedSecretResource.secretValueSECRET_VALUE
ExposedSecretResource.snippetSNIPPET
ExposedSecretResource.statusPROVIDER_STATUS
ExposedSecretResource.status (normalized)SOURCE_STATUS
ExposedSecretResource.tagsTAGS
ExposedSecretResource.targetAccountTARGET_ACCOUNT
ExposedSecretResource.typeEXPOSED_SECRET_TYPE
ExposedSecretResource.vendorHashVENDOR_HASH
ExposedSecretResource.exposureUrlEXPOSURE_URL
Generated (md5 of type and severity)TYPE
Generated (md5 of employee email and name)TARGETS
Generated (sync capture timestamp)LAST_CAPTURED
Exposed Secret Definition

Table 5: Exposed Secret Definition attribute mappings

Source Field NameSDM Attribute
ExposedSecretResource.exposedIdNAME
ExposedSecretResource.severitySEVERITY
ExposedSecretResource.severitySEVERITY_SCORE
ExposedSecretResource.severitySOURCE_SEVERITY
ExposedSecretResource.typeEXPOSED_SECRET_TYPE
Generated (md5 of type and severity)UID
Generated (sync capture timestamp)LAST_CAPTURED
NHI Token

Table 6: NHI Token attribute mappings

Source Field NameSDM Attribute
NHITokenResource.attributes.accountACCOUNT
NHITokenResource.attributes.accountNicknameACCOUNT_NICKNAME
NHITokenResource.attributes.createdDateCREATED_DATE
NHITokenResource.attributes.createdDateSOURCE_CREATED_DATE
NHITokenResource.attributes.entroTokenUrlENTRO_TOKEN_URL
NHITokenResource.attributes.entroUniqueIdentifierUID
NHITokenResource.attributes.environmentENVIRONMENT
NHITokenResource.attributes.expirationDateEXPIRATION_DATE
NHITokenResource.attributes.isActiveIS_ACTIVE
NHITokenResource.attributes.isAdminIS_ADMIN
NHITokenResource.attributes.lastActivityDateLAST_ACTIVITY_DATE
NHITokenResource.attributes.nhiNameNAME
NHITokenResource.attributes.nhiNameNHI_NAME
NHITokenResource.attributes.nhiStatusNHI_STATUS
NHITokenResource.attributes.nhiStatusPROVIDER_STATUS
NHITokenResource.attributes.nhiStatus (normalized)SOURCE_STATUS
NHITokenResource.attributes.nhiTypeNHI_TYPE
NHITokenResource.attributes.ownerOWNER
NHITokenResource.attributes.ownerEmailOWNER_EMAIL
NHITokenResource.attributes.sourceSystemSOURCE_SYSTEM
NHITokenResource.attributes.tagsTAGS
NHITokenResource.attributes.tokenTOKEN
NHITokenResource.attributes.urlURL
Generated (sync capture timestamp)LAST_CAPTURED
Risk

Table 7: Risk attribute mappings

Source Field NameSDM Attribute
RiskResource.categoryCATEGORIES
RiskResource.creationDateCREATION_DATE
RiskResource.creationDateSOURCE_CREATED_DATE
RiskResource.customerIdCUSTOMER_ID
RiskResource.detectionTimeDETECTION_TIME
RiskResource.detectionTimeFIRST_FOUND
RiskResource.exposureTimeEXPOSURE_TIME
RiskResource.exposureUrlsEXPOSURE_URLS
RiskResource.guidUID
RiskResource.hasWebhookMessageHAS_WEBHOOK_MESSAGE
RiskResource.isArchivedIS_ARCHIVED
RiskResource.modifyDateMODIFY_DATE
RiskResource.modifyDateSOURCE_LAST_MODIFIED
RiskResource.ownerOWNER
RiskResource.ownerUidOWNER_UID
RiskResource.pathPATH
RiskResource.payloadRESULTS
RiskResource.payload[].account.uidTARGETS
RiskResource.ruleCodeRULE_CODE
RiskResource.statusPROVIDER_STATUS
RiskResource.status (normalized)SOURCE_STATUS
RiskResource.tagsTAGS
RiskResource.typeRISK_TYPE
Generated (md5 of category, ruleCode, source, severity)TYPE
Generated (md5 of employee email and name)TARGETS
Generated (sync capture timestamp)LAST_CAPTURED
Risk Definition

Table 8: Risk Definition attribute mappings

Source Field NameSDM Attribute
RiskResource.mitigationMITIGATION
RiskResource.mitigationRECOMMENDATION
RiskResource.nameNAME
RiskResource.severitySEVERITY
RiskResource.severitySEVERITY_SCORE
RiskResource.severitySOURCE_SEVERITY
RiskResource.threatDescriptionDESCRIPTION
RiskResource.threatDescriptionTHREAT_DESCRIPTION
Generated (md5 of category, ruleCode, source, severity)UID
Generated (sync capture timestamp)LAST_CAPTURED

Operation options

The Entro Security connector supports the following operation options:

Table 9: Operation options

Connector ObjectOptionAll Possible ValuesDescriptionExample
Exposed Secret,
Exposed Secret Definition
severityUNKNOWN, LOW, MEDIUM, HIGH, CRITICALFilter by severity level.Key: severity Value: CRITICAL. Retrieves only exposed secrets with CRITICAL severity.
statusINVALID, ENABLED, DISABLED, UNSUPPORTED, UNREACHABLE, REVOKEDFilter by status.Key: status Value: ENABLED. Retrieves only exposed secrets with ENABLED status.
typeAny valid secret typeFilter by secret type.Key: type Value: GITHUB_API_TOKEN. Retrieves only GitHub API token exposed secrets.
NHI Tokenaccount_typeAny valid account typeFilter by account type.Key: account_type Value: AWS. Retrieves only NHI tokens associated with AWS accounts.
Risk,
Risk Definition
categoryCLOUD_SERVICE_RISKS, ABNORMAL_BEHAVIOR, MISCONFIGURATION, SECRET_HYGINE, EXPOSED_SECRET, LEAST_PRIVILEGE, MONITORINGFilter by risk category.Key: category Value: MONITORING. Retrieves only risks in the MONITORING category.
severityUNKNOWN, LOW, MEDIUM, HIGH, CRITICALFilter by severity level.Key: severity Value: CRITICAL. Retrieves only risks with CRITICAL severity.
statusOPEN, IN_PROGRESS, DISCARDED, MITIGATED, APPROVED, RESOLVEDFilter by risk status.Key: status Value: OPEN. Retrieves only risks with OPEN status.

APIs

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

Table 10: Entro Security API endpoints

Connector ObjectAPI Endpoint
AccountGET /v1/accounts
EmployeeGET /v1/employees
Exposed SecretGET /v1/exposed-secrets
Exposed Secret DefinitionGET /v1/exposed-secrets
NHI TokenGET /v1/identity-now/nhi
RiskGET /v1/risks
Risk DefinitionGET /v1/risks

Changelog

The Entro Security connector has undergone the following changes:

Table 11: Entro Security connector changelog

VersionDescriptionDate Published
3.0.0Initial Integration+ release.April 27th, 2026