Valence Security
Bring your Valence Security SaaS posture into JupiterOne: the SaaS applications Valence has discovered in your organization, with their sanctioned status, user count and discovery sources, and the Valence Posture security checks with the resources each failing check affects. Compare discovered apps against the applications you already ingest from your identity provider, and query open SaaS misconfigurations alongside the rest of your asset graph.
- Installation
- Authorization
- Data Model
- Types
Installation
This integration connects to the Valence Security Platform API (https://app.valencesecurity.com/api/v2) and ingests your discovered SaaS applications and your Valence Posture security checks, with an issue for each resource a failing check flags. It authenticates with a Valence API key, sent in the Authorization: Bearer <key> header, and only reads data. The integration is managed by JupiterOne and runs in the JupiterOne cloud, so no collector is needed.
Prerequisites
- A Valence Security tenant.
- A Valence admin who can create API keys.
- Access to JupiterOne with permission to configure integrations.
Configuration in Valence Security
Create the API key
- Sign in to the Valence Security console as an admin.
- Go to Admin > Access Management > API Keys.
- Click Generate API Key and enter a description and a display name, such as
JupiterOne. - Set Role to Viewer. Viewer is read-only, and the integration never changes data in Valence.
- Under Platforms, select the platforms whose security checks you want to ingest.
- Turn on Allow SaaS Apps access if you plan to enable the SaaS Applications data source. Without it, the SaaS apps API returns
403 Forbidden. - Click Generate, then copy the API key and store it somewhere safe.
The tenant name and domains are visible only to an Admin key. With a Viewer key, the valence_account entity is named after the integration instance; with an Admin key, it is named after the Valence tenant and also carries tenantName and domains.
Configuration in JupiterOne
To install the Valence Security integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Valence Security. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Valence Security account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen theAccountNametoggle is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. Valence refreshes its data about once a day, so a daily interval is usually enough. -
The Authentication fields below.
Authentication fields
| Field | Required | Description |
|---|---|---|
| API Key | Yes | The Valence API key created above. It is masked in JupiterOne. |
| Base URL | No | The Valence API base URL. Leave it empty to use https://app.valencesecurity.com/api/v2. Only https addresses on valencesecurity.com are accepted. |
When you save the instance, JupiterOne checks the filter values and reads one security check with the key. A wrong, expired or revoked key fails the check.
Filters
The filters narrow which Posture security checks are ingested. All values are selected by default.
| Field | Description | Default | Options |
|---|---|---|---|
| Security Check Severities | Security check severities to ingest. | All | Critical, High, Medium, Low |
| Security Check Statuses | Security check statuses to ingest. | All | Fail, Pass, Not applicable |
Narrowing a filter on an existing instance removes the checks and issues outside the selection from the graph on the next run.
Click Create once all values are provided to finalize the integration.
Data Sources
All data sources are disabled by default, so a new instance ingests only the valence_account and valence_service entities until you enable the ones you want. To enable them, open the instance, turn on the data sources under Data Sources, and save. They are ingested on the next run.
| Data Source | Description | Entities Created |
|---|---|---|
| SaaS Applications | SaaS applications Valence has discovered, with sanctioned status, user count, primary domain, categories, discovery sources, whether Valence connects to the app directly, and when the app was first used. Requires Allow SaaS Apps access on the API key. | valence_saas_application |
| Security Checks | Valence Posture security checks with title, platform, severity, status, summary and remediation steps, plus an issue for each resource a failing check flags. | valence_security_check, valence_issue |
Relationships are built only when the data source they need is enabled:
| Relationship | Requires |
|---|---|
valence_account PROVIDES valence_service | Always |
valence_account HAS valence_saas_application | SaaS Applications |
valence_saas_application IS Application (mapped) | SaaS Applications |
valence_account HAS valence_security_check | Security Checks |
valence_security_check IDENTIFIED valence_issue | Security Checks |
Notes
- Matching discovered apps to your applications. Each
valence_saas_applicationis linked with an IS relationship to an existingApplicationentity, such as an Okta or Microsoft Entra ID app, whosedisplayNameis exactly the Valence app name. The match is case-sensitive. The integration never creates the targetApplication; if no entity matches, no relationship is created. - Issues come from failing checks. Issues are created only for checks whose status is not Pass or Not applicable, and match the issues the Valence console shows for each check. An issue takes its severity from its check, and
resourceKindsays what it is about:identity: an identity account the check flags, such as an inactive admin or an account without MFA. The issue is named after the account email.integration: a third-party integration the check flags.- A related object kind, such as
policy: the object a configuration check flags. configuration: a configuration check that flags no specific object. The issue stands for the checked setting itself.
- Every run is a full sync. Apps, checks and issues that Valence no longer reports are removed from the graph on the next run.
- Raw data is not stored. Entities keep only the mapped properties.
Rate limits
The Valence API allows 400 requests per minute per user. A run makes one request for the tenant, one per 2,000 apps, one per 2,000 checks, and about one per failing check to list its issues. If Valence returns a rate-limit error, the integration waits until the limit resets and retries.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Endpoints
API endpoints that the integration makes requests to.
Show Endpoints (6)
https://app.valencesecurity.com/api/v2/identity/accountshttps://app.valencesecurity.com/api/v2/integrationshttps://app.valencesecurity.com/api/v2/saasapps/listhttps://app.valencesecurity.com/api/v2/securitychecks/listhttps://app.valencesecurity.com/api/v2/securitychecks/relatedObjectshttps://app.valencesecurity.com/api/v2/tenantconfiguration
Documentation Links
Links to provider documentation relevant to setup and configuration.
Show Documentation Links (1)
Per-Data-Source Breakdown
Authorization required by the steps that make up each data source. Steps that depend on a data source are listed in the Per-Step Breakdown; the complete lists are in the sections above.
Show all data sources (2)
| Data Source | Endpoints |
|---|---|
| SaaS Applications | https://app.valencesecurity.com/api/v2/saasapps/list |
| Security Checks | https://app.valencesecurity.com/api/v2/identity/accounts, https://app.valencesecurity.com/api/v2/integrations, https://app.valencesecurity.com/api/v2/securitychecks/list, https://app.valencesecurity.com/api/v2/securitychecks/relatedObjects |
Per-Step Breakdown
Detailed authorization requirements for each ingestion step.
Show all steps (1)
| Step | Endpoints |
|---|---|
| Build Check Issues | https://app.valencesecurity.com/api/v2/securitychecks/relatedObjects, https://app.valencesecurity.com/api/v2/identity/accounts, https://app.valencesecurity.com/api/v2/integrations |
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | valence_account | Account |
| Issue | valence_issue | Finding |
| SaaS Application | valence_saas_application | Application |
| Security Check | valence_security_check | Control |
| Service | valence_service | Service |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
valence_account | PROVIDES | valence_service |
valence_account | HAS | valence_saas_application |
valence_account | HAS | valence_security_check |
valence_security_check | IDENTIFIED | valence_issue |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
|---|---|---|---|
valence_saas_application | IS | application | FORWARD |
Valence Account
valence_account inherits from Account
| Property | Type | Description | Specifications |
|---|---|---|---|
domains | array | null | Domains bound to the Valence tenant. Only set when the API key can read the tenant configuration (Admin role). | |
tenantName | string | null | Valence tenant name. Only set when the API key can read the tenant configuration (Admin role). |
Valence Issue
valence_issue inherits from Finding
| Property | Type | Description | Specifications |
|---|---|---|---|
id * | string | Valence vuid of the affected resource; the check vuid for a configuration issue. | |
resourceKind | string | null | Kind of the affected resource: identity, integration, configuration, or the related object kind (for example policy). |
Valence Saas Application
valence_saas_application inherits from Application
| Property | Type | Description | Specifications |
|---|---|---|---|
categories | array | null | Valence app categories. | |
discoverySources | array | null | Detection sources that found the app (Integrations, IdP App, Email, CASB, BEX, Secure Browser, Platform monitored by Valence). | |
firstUsedOn | number | null | When Valence first observed the app in use (epoch ms). | |
isAICapable | boolean | null | Whether the app has an AI capability, per Valence. | |
isDirectlyConnected | boolean | null | Whether Valence has a direct connector to the app (a detection source of kind "Integrations"), as opposed to discovered-only. | |
primaryDomain | string | null | Primary domain of the application. | |
sanctioned | string | null | Sanctioned/unsanctioned marker for the application (vendor string). | |
sanctionedActor | string | null | Who set the sanctioned status, when recorded. | |
sanctionedExpiresOn | number | null | When the sanctioned status expires (epoch ms), when set. | |
sanctionedUpdatedOn | number | null | When the sanctioned status was last updated (epoch ms). | |
userCount | number | null | Number of users Valence observed using the application. |
Valence Security Check
valence_security_check inherits from Control
| Property | Type | Description | Specifications |
|---|---|---|---|
connectorDisplayName | string | null | Display name of the connector the check ran through. | |
platform | string | null | Platform the check applies to. | |
remediationSteps | string | null | Remediation steps for the check. | |
severity | string | null | Check severity, lowercased: critical, high, medium or low. | |
title | string | null | Human-readable title of the check. |
Valence Service
valence_service inherits from Service