mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-12 02:15:01 +00:00
Paul Gottschling
007a9be195
Continues the work from the previous batch (#67674). We are standardizing docs guides to add a `page_type` frontmatter field, with values for how-to guides, references, etc. We can then use this field to apply linting rules that ensure each guide type follows type-specific docs site conventions. The first convention is that each docs page must have an outcome statement, the structure of which depends on the guide's type. Human and AI agent readers can determine from the outcome statement whether to continue reading the guide or not. This change assigns the `page_type` frontmatter field to 46 guides. Where an outcome statement is missing, it adds one. Where an outcome statement exists, it ensures that the statement matches the standard structure so we can add a linter later on. Of the 46 guides: - 12 guides already included the expected outcome statement, but needed a `page_type` frontmatter field. - 19 guides included an outcome statement but required minor tweaks so they followed the expected structure. - 15 guides had no outcome statement at all.
37 lines
1.2 KiB
Plaintext
37 lines
1.2 KiB
Plaintext
---
|
|
title: Explore Access Paths and Activity
|
|
description: Explore identity risks and access pathways with dashboards, graph visualization, and SQL queries.
|
|
tags:
|
|
- conceptual
|
|
- identity-security
|
|
- access-risks
|
|
enterprise: Identity Security
|
|
page_type: landing
|
|
---
|
|
|
|
<Callout
|
|
variant="tip"
|
|
title="Did you know? Agent access paths and activity is part of a broader Agentic Identity Framework."
|
|
description="The Agentic Identity Framework is a standards-driven set of designs, SDKs, and reference implementations for deploying AI agents securely."
|
|
icon="gearStack"
|
|
link={{
|
|
title: "Explore framework",
|
|
href: "../../agentic-identity-framework",
|
|
}}
|
|
/>
|
|
|
|
Teleport Identity Security helps teams expose and eliminate hidden risk in their infrastructure.
|
|
|
|
These are some use cases for Teleport Identity Security:
|
|
|
|
- Find users with the highest standing privilege with the Standing Privilege Dashboard.
|
|
- Visually understand which resources a user can access and which users and bots can access a resource.
|
|
- Quickly query key access pathways with SQL Editor.
|
|
- Know when access pathways change for a critical asset with Crown Jewel Alerting.
|
|
- Investigate identity breaches by correlating audit logs from across your
|
|
infrastructure.
|
|
|
|
## Guides
|
|
|
|
<DocCardList />
|