/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Israel-based Orchid Security, which uses LLMs to identify clients' security requirements, emerges from stealth with a $36M seed led by Team 8 and Intel Capital

- Each of those applications require different identity management configurations—such as multi-factor authentication …

Axios Sam Sabin

Context & Ripple Effects

Orchid enters an identity-security cluster that has expanded from third-party application access management to non-human identity management and enterprise identity management. That progression makes configuration requirements across applications a consequential operational layer, not merely a policy task.

The round also pairs Team 8 with Intel Capital behind a company focused on using LLMs to identify those requirements, giving the approach early backing in a crowded identity-security field.

First-order effects

  • Orchid gains $36M in seed funding and the backing of Team 8 and Intel Capital as it emerges from stealth.
  • Organizations evaluating Orchid can use its LLM-led approach to surface security requirements tied to differing application identity configurations, including multi-factor authentication.

Second-order effects

  • Identity-management vendors, including companies addressing enterprise identity management, face added pressure to show how their products translate security requirements into workable configurations.
  • The funding validates requirement discovery as an adjacent layer of the identity stack, potentially broadening buyer evaluations beyond point tools for specific identity categories.

Third-order effects

  • If customers adopt automated requirement discovery, identity security could shift toward a more agentic control plane that connects application context, policy requirements and configuration decisions.
  • That shift would raise the importance of trust, explainability and human oversight around LLM-generated security guidance, since configuration choices directly affect access controls.

The trend: Identity security is moving from managing discrete credential and access categories toward AI-assisted interpretation and enforcement of application-specific security requirements.