PCI-7.2:

From HORSE - Holistic Operational Readiness Security Evaluation.
Revision as of 14:10, 1 March 2007 by Mdpeters (talk | contribs) (New page: <blockquote style="background: #C8CDC7; padding: 1em; margin-left: 0.5em;"> <br> :'''Establish a mechanism for systems with multiple users that restricts access based on a user’s need to...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Establish a mechanism for systems with multiple users that restricts access based on a user’s need to know, and is set to “deny all” unless specifically allowed.


PCI-7.2: Examine system settings and vendor documentation to verify there is an access control system in place, and that it is implemented to include the following:


  • Coverage of all system components.
  • Assignment of privileges to individuals based on job classification and function.
  • “Deny-all” setting by default (some access control systems are set by default to “allow-all” thereby allowing access unless/until a rule is written to specifically deny it).



Testing Procedures

Insert testing guidance here.

Testing Frequency

Describe testing frequency here.

Evidence Archive Location

Insert hyperlink or location of evidence archive.

Control Stewards Process Narrative

Provide control steward commentary indicating the formal methodology in place.


Control Steward – Jon Doe

Process Illustration

Replace this test by inserting a process diagram, flowchart or other visual representation to illustrate the process narrative as necessary. Include a brief description of the process illustration.

Control Status and Auditors Commentary

The control is effective.


File:Greenlock.jpg

Status is acceptable.

Control Exception Commentary

Status is acceptable.

Remediation Plan

Remediation is not required at this time.


--Mdpeters 09:10, 1 March 2007 (EST)