Frameworks & Standards
IDESG / IDEF
The Identity Ecosystem Steering Group focused on trusted digital identity, including privacy, security, interoperability, usability, and accountability. Its Identity Ecosystem Framework is useful as an assessment lens when buyers ask how identity and data control work across parties.
Buyer question
"Can we identify who has access and who is responsible for actions across our collaboration partners?"
Legra fit
| Assessment area | Legra fit | Status |
|---|---|---|
| Individual and organizational identity | Legra uses decentralized identifiers for humans, organizations, nodes, software agents, and AI agents. | Native fit |
| Privacy and minimization | Encrypted workspaces and scoped membership reduce exposure to infrastructure operators and unrelated parties. | Native fit |
| Interoperability | DIDs, RDF, PROV-style provenance, and standards-based graph metadata support cross-party identity context. | Partial fit |
| Accountability | Signed commits, branch history, task provenance, and events can show who changed what, when, and under which authority. | Native fit |
| Enterprise identity bridges | Mapping Active Directory, OAuth/OIDC, or other enterprise identity sources into Legra DIDs and delegations is an integration pattern that each deployment configures. | External responsibility |
What Legra can say
Use workspace membership, delegated access, and change history to review who can act and what they have done. Connect these records to the identity and account-management processes your organization uses.
This gives buyers evidence for:
- Who owns or controls a workspace.
- Which DIDs had access at a point in time.
- Which actor authored a commit.
- Whether an action came directly from a person, organization, software agent, or delegated authority.
- How identity and provenance travel with the data instead of living only in an external IAM system.
Assessment boundary
IDESG / IDEF-style assessment depends on the complete identity ecosystem: organizational policy, identity proofing, relying-party agreements, wallet or credential processes, and user experience. Legra contributes identity, delegation, provenance, and access controls within that broader trust framework.