Skip to main content

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​

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​

  1. Sign in to the Valence Security console as an admin.
  2. Go to Admin > Access Management > API Keys.
  3. Click Generate API Key and enter a description and a display name, such as JupiterOne.
  4. Set Role to Viewer. Viewer is read-only, and the integration never changes data in Valence.
  5. Under Platforms, select the platforms whose security checks you want to ingest.
  6. 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.
  7. 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.AccountName when the AccountName toggle 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 DISABLED and 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​

FieldRequiredDescription
API KeyYesThe Valence API key created above. It is masked in JupiterOne.
Base URLNoThe 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.

FieldDescriptionDefaultOptions
Security Check SeveritiesSecurity check severities to ingest.AllCritical, High, Medium, Low
Security Check StatusesSecurity check statuses to ingest.AllFail, 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 SourceDescriptionEntities Created
SaaS ApplicationsSaaS 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 ChecksValence 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:

RelationshipRequires
valence_account PROVIDES valence_serviceAlways
valence_account HAS valence_saas_applicationSaaS Applications
valence_saas_application IS Application (mapped)SaaS Applications
valence_account HAS valence_security_checkSecurity Checks
valence_security_check IDENTIFIED valence_issueSecurity Checks

Notes​

  • Matching discovered apps to your applications. Each valence_saas_application is linked with an IS relationship to an existing Application entity, such as an Okta or Microsoft Entra ID app, whose displayName is exactly the Valence app name. The match is case-sensitive. The integration never creates the target Application; 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 resourceKind says 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.