User manual

Understanding how security policies are authenticated on
a server
In addition to allowing the reuse of the same security settings, policies stored on Adobe
Policy Server have the added benefit of letting you expire and revoke documents no
matter how many copies were created or distributed, maintain accountability by auditing
who opens protected documents, and retain usage flexibility.
Security policies A. Policies are stored on the server. B. Policies are applied to the PDF
document. C. Users can open, edit, and print the document only if permitted by the policy.
The process of using server-based security policies requires four main stages:
Configuring the policy server
The system administrator of your company or group usually configures Adobe Policy
Server, manages accounts, and sets up organizational policies. For more information on
configuring the policy server, see the Adobe website.
Publishing a document with a security policy
An author creates a PDF document and applies a policy stored on Adobe Policy Server to
the document. The policy server generates a license and unique encryption key for the
document. Acrobat embeds the license in the document and encrypts it using the
encryption key. The author or administrator can use this license to track and audit the
document.
Viewing a document with a policy applied
When users try to open the secure document in Acrobat 7.0 (or Adobe Reader 7.0), they
must authenticate their identities. If the user is granted access to the PDF document, the
document is decrypted and opens with whatever permissions are specified in the policy.
Administering events and modifying access
Using the Web Console, the author or administrator can track events and change access to
policy-secured documents. Administrators can view all document and system events,
modify configuration settings, and change access to policy-secured documents. Users may
be required to check in the PDF document periodically to continue to have access to the
file. (See Using Adobe Policy Server.)