12.07.2015 Views

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Securing HFS FunctionsKeywordALLCONTROLDescriptionAllows all of the above.A special access not used <strong>for</strong> normal file accessvalidation. This is used with HFS function security toallow a user to change file attributes. Morein<strong>for</strong>mation can be found in the following section.ReportingAudit records created by HFS file access checks, (i.e., violations, <strong>and</strong> auditevents) are written to the Audit Tracking File <strong>and</strong> accessed by the TSSUTILreport utility. TSSUTIL integrates these events among other events according tothe report generation criteria.Securing HFS FunctionsIn addition to file access security, HFS functions can also be secured. Thesefunctions can be a system action, such as setting a ptrace or a job’s priority, orthey can be file-related, such as changing the file mode or audit settings.A system function is secured by a rule in the IBMFAC class, while a file-relatedfunction is secured by a combination of an IBMFAC class rule <strong>and</strong> a HFS fileresource rule. By following this approach, changes to file attributes can bepermitted at a global basis, or restricted to a particular file.The resource name <strong>for</strong>mat <strong>for</strong> HFS IBMFAC rules is: BPX.<strong>CA</strong>HFS.function. Anexample of a permission would be:TSS PER(USER01) IBMFAC(BPX.<strong>CA</strong>HFS.function) ACCESS(READ)System FunctionsIn order to per<strong>for</strong>m a system function, the user requires READ access to thecorresponding IBMFAC.Controlling Access to the Hierarchical File System 2–7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!