Skip to content

Commit d15dfa1

Browse files
Update intro
1 parent e6ccc09 commit d15dfa1

File tree

1 file changed

+23
-12
lines changed

1 file changed

+23
-12
lines changed

content/manuals/security/for-admins/domain-audit.md

Lines changed: 23 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,17 @@ weight: 50
1111

1212
{{< summary-bar feature_name="Domain audit" >}}
1313

14-
Domain management identifies uncaptured users in an organization. Uncaptured users
15-
are Docker users who have authenticated to Docker using an email address
16-
associated with one of your verified domains, but they're not a member of your
17-
organization in Docker. You can audit domains on organizations that are part of
18-
the Docker Business subscription. To upgrade your existing account to a Docker
19-
Business subscription, see [Upgrade your subscription](/subscription/upgrade/).
20-
21-
Uncaptured users who access Docker Desktop in your environment may pose a
22-
security risk because your organization's security settings, like Image Access
14+
Domain management identifies uncaptured users in an organization. Uncaptured
15+
users are Docker users who have logged into Docker using an email address
16+
associated with one of your verified domains, but are not a member of your
17+
organization in Docker. To manage your organization, domain management allows
18+
you to:
19+
20+
- Audit domains for uncaptured users
21+
- Auto-provision users to an organization
22+
23+
Uncaptured users who access Docker Desktop may pose a security risk because
24+
your organization's security settings, like Image Access
2325
Management and Registry Access Management, aren't applied to a user's session.
2426
In addition, you won't have visibility into the activity of uncaptured users.
2527
You can add uncaptured users to your organization to gain visibility into their
@@ -34,7 +36,7 @@ associated with one of your verified domains
3436
Although domain audit can't identify all Docker users in your environment, you
3537
can enforce sign-in to prevent unidentifiable users from accessing Docker
3638
Desktop in your environment. For more details about enforcing sign-in, see
37-
[Configure registry.json to enforce sign-in](../for-admins/enforce-sign-in/_index.md).
39+
[Enforce sign-in for Docker Desktop](../for-admins/enforce-sign-in/_index.md).
3840

3941
> [!TIP]
4042
>
@@ -50,7 +52,7 @@ version of Docker Desktop, and enable you to [enforce sign-in](enforce-sign-in/_
5052
5153
## Prerequisites
5254

53-
Before you audit your domains, review the following required prerequisites:
55+
Before managing domains, review the following required prerequisites:
5456

5557
- Your organization must be part of a Docker Business subscription. To upgrade
5658
your existing account to a Docker Business subscription, see
@@ -80,7 +82,16 @@ your existing account to a Docker Business subscription, see
8082

8183
## Auto-provisioning
8284

83-
Auto-provisioning adds users automatically to your organization.
85+
Auto-provisioning adds users to your organization when they sign in with an
86+
email address that matches a verified domain. This relies on domain
87+
verification, which confirms that your organization controls the domain. Once
88+
a domain is verified, Docker can automatically associate matching users with
89+
your organization. For more information on verifying a domain, see
90+
[Verify your domain](/manuals/security/for-admins/single-sign-on/configure/#step-two-verify-your-domain).
91+
92+
This simplifies user management, helps apply organization-level security
93+
settings consistently, and reduces the risk of uncaptured users accessing
94+
Docker services without visibility or controls.
8495

8596
> [!IMPORTANT]
8697
>

0 commit comments

Comments
 (0)