Operation Manual

322
Security
Last updated 4/7/2015
Enable Menu Items JavaScript Execution Privileges Enables executing JavaScript by clicking menu items. When off,
privileged JavaScript calls can be executed through the menu. Executing non-privileged JavaScript calls through
menu items is not blocked whether this box is checked or not.
Enable Global Object Security Policy Allows JavaScript globally through APIs, or trusts specific documents
containing JavaScripts.
Alternatively, you can modify your system registry settings to manage JavaScript execution.
For details, see the Application Security Guide at www.adobe.com/go/learn_acr_appsecurity_en.
Choosing a security method for PDFs
Note: For a full list of articles about security, see Overview of security in Acrobat DC and PDF content .
By adding security to documents, you can limit viewing, editing, printing, and other options to only the specified users.
Choosing which type of security to use
Security features range from relatively simple measures to sophisticated systems adopted by corporations and agencies.
Which feature you choose depends on what you want to achieve. Here are some examples:
• You want only certain people to view your PDF. The easiest solution is to add a password to the PDF and send it
to your intended recipients. (See
Password security and restricting printing, editing, and copying.)
• You don’t want anyone to print or edit your PDF. You can block printing and editing from the same dialog box
that you use to add a password. (See
Password security and restricting printing, editing, and copying.)
• You want to assure your recipients that the PDF is really from you. The best way is to purchase a digital ID from
a certificate authority. Alternatively, you can create a self-signed digital ID if you are communicating with a group
that you trust. (See
About digital IDsand Securing documents with certificates .)
• You want an organization-wide security solution for PDFs. You can devise a solution specifically for a company
handling sensitive data. Some organizations use Adobe LiveCycle Rights Management ES to apply a policy to
documents. The policy contains the list of recipients and their individual set of permissions. Individuals can use a
policy to apply the same security settings to numerous documents. (See
Securing documents with Adobe LiveCycle
Rights Management ES .)
Security policies
A security policy enforces systematic constraints on information flow and exchange within an organization. You can
use Adobe LiveCycleRights Management ES to apply a policy to documents without the need for digital signatures and
certificates. If you often apply the same security settings to PDFs, consider creating a security policy to simplify your
workflow. Different policies are useful for accommodating different requirements.
Envelope policy You can secure multiple documents by embedding them in a PDF envelope. You can encrypt
envelopes to prevent unauthorized users from accessing the contents and certify them to provide proof of origin.
Authorized recipients can open the envelope and extract the files to view them.
LiveCycle Rights Management ES policy Adobe LiveCycleRights Management ES policies are stored on a server, and
users must have access to the server to use them. Creating these policies requires specifying the document recipients
from a list on Adobe LiveCycleRights Management ES.
Password and certificate policies Save your password or certificate settings and reuse them to encrypt PDFs without
setting up the password or certificate for each instance.