About Living Security
Living Security sells a platform that reads signals from the security tools its customers already run to reveal human and agent risk, and guides the response. Living Security states that humans and AI agents now share access, data, and decisions. Living Security says human risk management was built on the assumption that the identity taking an action is a person, and that the assumption no longer holds. Living Security describes an AI agent as an identity that has credentials, does things that cannot be fully predicted, and can move risk as fast and as much as a person can. Living Security notes that AI agents have permissions, touch data and take action.[5][7]
Living Security joins hundreds of human risk signals from the security and HR tools customers already use, per person, with Livvy guiding the response. Living Security weighs threat, access and behavior so that the riskiest few people rise first. In the Living Security model, signals from nine risk domains join into cohorts, cohorts feed sequences, and each sequence heads for a breach scenario. The Living Security map of how risk builds comes from the Human Risk Management Framework, which has 137 signals and is open to everyone under CC BY 4.0. In one Living Security example, four signals from email security and the identity provider reach an accounts payable lead in Finance, and that person's priority rises to High.[5]
Livvy proposes the next move, and the customer's team approves it. Livvy recommends an action for each person, a playbook runs the action, and every result flows back into the Human Risk Index. Living Security guides or runs approved responses, and approvals stay with the customer's team. Livvy can recommend step-up MFA and a credential reset for a person, then a 90-second coaching nudge, and waits for the team's approval. Living Security says that when an employee's score moves, the response moves with it, and the response can be coaching, tightening the person's authentication or changing what the person can access.[3][5][7]
Living Security offers phishing simulation aimed by the customer's risk data, not its calendar. For a Living Security phishing simulation, who is being targeted by real attacks, what assets those users can access and how they have behaved in the past go into shaping the test before it goes out. Living Security is launching support for phishing simulations via email and Teams. Living Security places SMS, voice, and video simulations on its near-term roadmap. In a playbook Living Security demonstrated, everyone who clicked gets training and the whole team gets a nudge. Access tightens on its own for the people who clicked in a playbook Living Security demonstrated.[5][7]
Living Security offers AI calls and two-way texts that talk back, then coach. Living Security offers a library aimed by risk and delivered by playbooks. Living Security takes content from threat to training that is on brand and approved by the customer. Living Security offers team escape rooms and a tabletop for practicing the breach. Living Security offers a way to see the shadow AI and to hold every agent to an accountable owner.[5]
Microsoft Entra ID can contribute normalized identity, sign-in, risk, device, and attack-simulation activity to Living Security. With a Microsoft Entra ID permission for group membership actions, a Living Security playbook can add a person to, or remove them from, a Microsoft Entra ID group. For group membership actions on the Microsoft Entra ID connection, an administrator chooses an explicit allowlist of groups on the connection. A Living Security customer can invite a system admin into the platform with scoped permissions, so that the admin enters integration credentials directly.
SailPoint Identity Security Cloud and IdentityIQ manage Living Security accounts through the SailPoint SCIM 2.0 connector. Living Security SCIM follows the SCIM 2.0 standard (RFC 7643 and RFC 7644). When a source sends a custom extension attribute for the first time, Living Security adds that extension. Living Security holds some changes that succeed in SailPoint, for example a change that would remove the customer's last owner.[3][5][8]
Living Security on the record