/
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

Tel Aviv-based Astrix Security, which helps firms secure access to API keys, service accounts, secrets, and more, raised a $45M Series B led by Menlo Ventures

Ryan Naraine / SecurityWeek :

SecurityWeek Ryan Naraine

Context & Ripple Effects

Astrix's financing follows its emergence with $15M for access management of third-party integrations and a subsequent $25M Series A for securing those integrations. The progression broadens the relevant access surface from connected applications to credentials such as API keys, service accounts and secrets.

The round matters because these machine and integration credentials sit outside traditional employee-login controls. It places Astrix in the same wider access-security field as platforms focused on SaaS and cloud access exposure.

First-order effects

  • Astrix gains $45M in new capital to build and commercialize controls for API keys, service accounts, secrets and related access paths.
  • Menlo Ventures deepens its position in Astrix by leading the Series B, tying the investor more directly to the company's next stage of execution.

Second-order effects

  • A better-funded Astrix raises competitive pressure on vendors securing SaaS integrations and cloud access surfaces to show how their products handle nonhuman credentials as well as user access.
  • Security teams evaluating integration governance gain another well-capitalized supplier focused on the credentials that enable applications and automated services to connect.

Third-order effects

  • If this funding pattern persists, identity security is likely to be defined less narrowly around employee authentication and more around governing every software-held credential and integration.
  • The category could increasingly converge around a shared control plane for SaaS integrations, secrets and machine identities, though the corpus does not establish which product boundary will win.

The trend: Security investment is shifting toward access controls for machine identities and application integrations, where API keys, service accounts and secrets create a growing operational boundary.