Frequently Asked Question
What does "Duly Authorized Officer" mean?
In the context of PCI SSC-related validation and compliance reports, the intent of requiring a signature from a "duly authorized officer" is to ensure the Company is aware of and has formally signed off on the work being done together with all associated Company liability for that work. A "duly authorized officer" must have authority to legally bind the company for purposes of the report. Although the signatory's job title need not include the term "officer," the signatory must be formally authorized by the Company to sign such documents on the Company's behalf and should be competent and knowledgeable regarding the applicable PCI SSC program and related requirements and duties. Each organization is different and is ultimately responsible for defining its own policies and job functions based on the Company's needs and culture.
Examples of signatories that are not "duly authorized officers" include non-employees, attestants or notaries, and any other individual (whether employed by the Company or not) who either is not authorized to make binding commitments on the Company's behalf and/or are merely attesting to the genuineness of the document or signature by adding their own signature. Signature authority for materials submitted to PCI SSC may not be outsourced to any third party.
This FAQ applies to all PCI SSC programs. Refer to each applicable PCI SSC program guide, available on the PCI SSC website, for any additional context for a duly authorized officer.
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
Where can I find the current version of PCI DSS?
-
Why are there multiple PCI DSS Self-assessment Questionnaires (SAQs)?
-
What is a PCI DSS Self-Assessment Questionnaire?
-
Are Mobile Payments on COTS (MPoC) solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?
-
How can an entity meet PCI DSS requirements for PAN masking and truncation if it has migrated to 8-digit BINs?