@@ -10,27 +10,44 @@ and manage the Docker images you use in your applications.
10
10
11
11
## Image management
12
12
13
- Docker Trusted Registry can be installed on-premises, or on a virtual private
13
+ DTR can be installed on-premises, or on a virtual private
14
14
cloud. And with it, you can store your Docker images securely, behind your
15
15
firewall.
16
16
17
- ![ ] ( images/overview-1.png )
18
-
19
17
You can use DTR as part of your continuous integration, and continuous
20
- delivery processes to build, run, and ship your applications.
18
+ delivery processes to build, ship and run your applications.
21
19
20
+ DTR has a web based user interface that allows authorized users in your
21
+ organization to browse docker images. It provides information about
22
+ who pushed what image at what time. It even allows you to see what dockerfile
23
+ lines were used to produce the image and, if security scanning is enabled, to
24
+ see a list of all of the software installed in your images.
22
25
23
- ## Built-in security and access control
26
+ ## Built-in access control
24
27
25
28
DTR uses the same authentication mechanism as Docker Universal Control Plane.
26
- It has a built-in authentication mechanism, and also integrates with LDAP
27
- and Active Directory. It also supports Role Based Access Control (RBAC).
28
-
29
- This allows you to implement fine-grain access control policies on who has
30
- access to your Docker images.
31
-
32
- ![ ] ( images/overview-2.png )
33
-
29
+ Users can be managed manually or syched from LDAP or Active Directory. DTR
30
+ uses [ Role Based Access Control] ( admin/manage-users/index.md ) (RBAC) to allow you to implement fine-grained
31
+ access control policies for who has access to your Docker images.
32
+
33
+ ## Security scanning
34
+
35
+ DTR has a built in security scanner that can be used to discover what versions
36
+ of software are used in your images. It scans each layer and aggregates the
37
+ results to give you a complete picture of what you are shipping as a part of
38
+ your stack. Most importantly, it co-relates this information with a
39
+ vulnerability database that is kept up to date through [ periodic
40
+ updates] ( admin/configure/set-up-vulnerability-scans.md ) . This
41
+ gives you [ unprecedented insight into your exposure to known security
42
+ threats] ( user/manage-images/scan-images-for-vulnerabilities.md ) .
43
+
44
+ ## Image signing
45
+
46
+ DTR ships with [ Notary] ( ../../../notary/getting_started/ )
47
+ built in so that you can use
48
+ [ Docker Content Trust] ( ../../../engine/security/trust/content_trust/ ) to sign
49
+ and verify images. For more information about managing Notary data in DTR see
50
+ the [ DTR-specific notary documentation] ( user/manage-images/manage-trusted-repositories.md ) .
34
51
35
52
## Where to go next
36
53
0 commit comments