In short: Obsidian Security (independent; venture-backed, Series D; founded 2017) and Valence Security (independent; venture-backed, Series A; founded 2021) both publish documentation for 10 of the 21 NHI capabilities we track. The public evidence differs on 5: evidence for Obsidian Security only on attribution to humans and authorization policy; evidence for Valence Security only on ownership assignment, service accounts and API keys. Records checked 16 October 2026. This is a reading of what each company has published, not a score or a recommendation.
This page puts two company records side by side. It shows what public evidence establishes for each, using the same labels as the profiles. It gives no score, no ranking and no recommendation. Read the full records for sources: Obsidian Security and Valence Security.
Company facts
Scroll sideways to see all columns.
| Fact | Obsidian Security | Valence Security |
|---|---|---|
| Record name | Obsidian Security | Valence Security |
| Ownership | Independent | Independent |
| Stage | Venture-backed, Series D | Venture-backed, Series A |
| Founded | 2017, by Ben Johnson, Glenn Chisholm and Matt Wolff (formerly of Carbon Black and Cylance) (Publicly disclosed) | 2021 (Publicly disclosed) |
| Headquarters | Palo Alto, California, USA (Publicly disclosed) | Not stated on the company website. Press release datelines: Tel Aviv (2021), San Francisco (2022), New York (2025) (Sources conflict) |
| Total funding | About $205M (as reported by BankInfoSecurity) (Publicly disclosed) | $32M (as stated in October 2022) (Verified) |
| Categories in our directory | SaaS security, NHI security (third-party apps), AI agent security | SaaS security posture, SaaS identity threat detection, AI security posture (SaaS) |
| Record verified | 2026-10-16 | 2026-10-16 |
Why these two are compared
Each record lists the other as a direct competitor in our analysis of product scope.
- The Obsidian Security record describes Valence Security as: SaaS posture, integrations and non-human identities.
- The Valence Security record describes Obsidian Security as: SaaS posture, integration risk and AI agent security.
Capability evidence, side by side
Documented by vendor means the company's own documentation describes the capability. It is not independent verification and says nothing about depth. Not publicly verified means we did not find public documentation. It does not mean the product lacks the capability.
Scroll sideways to see all columns.
| Capability | Obsidian Security | Valence Security |
|---|---|---|
| NHI discovery | Documented by vendor | Documented by vendor |
| NHI inventory | Documented by vendor | Documented by vendor |
| Ownership assignment | Not publicly verified | Documented by vendor |
| Attribution to humans | Documented by vendor | Not publicly verified |
| Access analysis | Documented by vendor | Documented by vendor |
| Authorization policy | Documented by vendor | Not publicly verified |
| Least privilege | Documented by vendor | Documented by vendor |
| Lifecycle management | Not publicly verified | Not publicly verified |
| Credential rotation | Not publicly verified | Not publicly verified |
| Secrets management | Not publicly verified | Not publicly verified |
| Certificate management | Not publicly verified | Not publicly verified |
| Service accounts | Not publicly verified | Documented by vendor |
| API keys | Not publicly verified | Documented by vendor |
| OAuth apps and tokens | Documented by vendor | Documented by vendor |
| Workload identity | Not publicly verified | Not publicly verified |
| Cloud identity | Not publicly verified | Not publicly verified |
| AI agents | Documented by vendor | Documented by vendor |
| Agent governance | Documented by vendor | Documented by vendor |
| Monitoring and detection | Documented by vendor | Documented by vendor |
| Remediation | Documented by vendor | Documented by vendor |
| Audit evidence | Documented by vendor | Documented by vendor |
Where the public evidence differs
- Public evidence found for Obsidian Security and not for Valence Security: Attribution to humans, Authorization policy.
- Public evidence found for Valence Security and not for Obsidian Security: Ownership assignment, Service accounts, API keys.
- Public evidence found for both: NHI discovery, NHI inventory, Access analysis, Least privilege, OAuth apps and tokens, AI agents, Agent governance, Monitoring and detection, Remediation, Audit evidence.
- Not established for either from public sources: Lifecycle management, Credential rotation, Secrets management, Certificate management, Workload identity, Cloud identity.
A difference in this list is a difference in what each company has published, as read by us on the verification dates above. It is not a count of features and should not be read as a score. Confirm any capability that matters to you with the vendor and in a proof of concept.
Recent developments
Obsidian Security
- 4 August 2026: $85M Series D led by Crescent Cove Advisors at a stated $1.1B valuation. All existing investors participated. The company said the funds support growth in AI agent security. [source]
- 24 February 2026: ISO/IEC 42001:2023 certification announced. The company named A-LIGN as the certification body and said the scope covers its SaaS security platform service. [source]
- 22 January 2026: SaaS supply chain security offering announced. The release describes integration risk visibility, prevention, breach detection and impact forensics, with Seagate and Wyndham executives quoted. [source]
Valence Security
- 21 July 2026: Integration with Anthropic's Claude Compliance API announced. A company post describes visibility into Claude Enterprise and Claude Platform usage, including the human and non-human identities with access. [source]
- 5 May 2025: State of SaaS Security report for 2025 to 2026 published with the Cloud Security Alliance. The company reports that 46% of organisations surveyed struggle to monitor non-human identities. These are survey figures published by the company. [source]
- 28 January 2025: Reseller partnership with GuidePoint Security announced. GuidePoint customers can buy the Valence platform through the reseller. [source]
Positioning
Obsidian Security
What the company says: Obsidian says it secures non-human identities and AI agents across third-party applications, and that agents must be controlled before misuse, not after. [source]
Our analysis: Obsidian addresses the identities that SaaS applications create themselves: OAuth grants, integrations, tokens and, more recently, AI agents. Its documented product answers which integrations and agents exist, who created them, what scope they hold and whether their behaviour is anomalous. It works inside SaaS and AI platforms, not across cloud infrastructure or secrets stores.
Valence Security
What the company says: Valence describes itself as a SaaS and AI security platform that finds and fixes risks across applications, configurations, identities and AI agents, with remediation that involves business users. [source]
Our analysis: Valence addresses non-human identities that live inside SaaS: third-party integrations, OAuth grants, service accounts and AI agents. Its documented product finds them, assesses their permissions and offers workflows to reduce or remove access. It does not present itself as a cross-environment NHI inventory or as a credential manager.
Common questions
What is the difference between Obsidian Security and Valence Security?
Obsidian addresses the identities that SaaS applications create themselves: OAuth grants, integrations, tokens and, more recently, AI agents. Its documented product answers which integrations and agents exist, who created them, what scope they hold and whether their behaviour is anomalous. It works inside SaaS and AI platforms, not across cloud infrastructure or secrets stores. Valence addresses non-human identities that live inside SaaS: third-party integrations, OAuth grants, service accounts and AI agents. Its documented product finds them, assesses their permissions and offers workflows to reduce or remove access. It does not present itself as a cross-environment NHI inventory or as a credential manager. In published documentation, public evidence was found for Obsidian Security and not for Valence Security on attribution to humans and authorization policy; for Valence Security and not for Obsidian Security on ownership assignment, service accounts and API keys. That is a difference in what each company has published, not a feature count or a ranking.
Who owns Obsidian Security and Valence Security?
Obsidian Security: Independent. Valence Security: Independent. Ownership is taken from company announcements and filings and is dated on each record.
Do Obsidian Security and Valence Security support AI agents?
AI agents: Obsidian Security, documented by vendor; Valence Security, documented by vendor. Agent governance: Obsidian Security, documented by vendor; Valence Security, documented by vendor.
Which is better, Obsidian Security or Valence Security?
We do not rank or recommend either company, and no company pays for coverage. The better fit depends on which identity types you need covered, where your credentials live, and what evidence your auditors expect. Put the questions on this page to both vendors and confirm the capabilities that matter in a proof of concept.
What are the alternatives to Obsidian Security and Valence Security?
Other companies in the same categories of our directory, listed alphabetically and not ranked: AppOmni, Cisco Identity Intelligence and Duo, CrowdStrike Falcon Next-Gen Identity Security, Grip Security, Nudge Security, Reco, Semperis and Silverfort, and 3 more in the company directory. Each has a sourced record on this site.
Questions to put to both
- Which identity types are discovered without an agent or manual import, and which need configuration?
- How is a named human owner assigned to each non-human identity, and what happens when that person leaves?
- What evidence can be exported for an audit, and in what format?
- Which capabilities are generally available today, and which are in preview?
- Who owns the company today, and what has been said about the product roadmap since any change of ownership?
See the methodology for how records are researched, and the list of all comparisons.