pci compliance

Payment Card Industry (PCI) Data Security Standard

Document Includes:

PCI DSS (PCI Data Security Standard Requirements and Security Assessment
Procedures) Guidance on Scoping
Guidance on the intent of all PCI DSS Requirements
Details of testing procedures
Guidance on Compensating Controls
SAQ Instructions and Guidelines
documents
Information about all SAQs and their eligibility criteria
How to determine which SAQ is right for your
organization
PCI DSS and PA-DSS Glossary of
Terms, Abbreviations, and Acronyms
Descriptions and definitions of terms used in the PCI
DSS and self-assessment questionnaires
These and other resources can be found on the PCI SSC website (www.pcisecuritystandards.org).
Organizations are encouraged to review the PCI DSS and other supporting documents before beginning
an assessment.
Expected Testing
PCI DSS, and provide a high-level description of the types of testing activities that should be performed in
order to verify that a requirement has been met. Full details of testing procedures for each requirement
can be found in the PCI DSS.

PCI DSS v3.2 SAQ A, Rev. 1.1 January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page v

Completing the Self-Assessment Questionnaire
For each question, status regarding that
requirement. Only one response should be selected for each question.
A description of the meaning for each response is provided in the table below:
Response When to use this response:
Yes The expected testing has been performed, and all elements of the
requirement have been met as stated.
Yes with CCW
(Compensating
Control Worksheet)
The expected testing has been performed, and the requirement has
been met with the assistance of a compensating control.
All responses in this column require completion of a Compensating
Control Worksheet (CCW) in Appendix B of the SAQ.
Information on the use of compensating controls and guidance on how
to complete the worksheet is provided in the PCI DSS.
No Some or all elements of the requirement have not been met, or are in
the process of being implemented, or require further testing before it will
be known if they are in place.
N/A
(Not Applicable)
The requirement does not apply to the environment. (See
Guidance for Non-Applicability of Certain, Specific Requirements below
for examples.)
All responses in this column require a supporting explanation in
Appendix C of the SAQ.
Guidance for Non-Applicability of Certain, Specific Requirements
If any requirements are deemed not applicable to your environment, select the
specific requirement, and –
entry.
Legal Exception
If your organization is subject to a legal restriction that prevents the organization from meeting a PCI DSS
PCI DSS v3.2 SAQ A, Rev. 1.1 Section 1: Assessment Information January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 2
Part 2b. Description of Payment Card Business
How and in what capacity does your business
store, process and/or transmit cardholder data?
Part 2c. Locations
List types of facilities (for example, retail outlets, corporate offices, data centers, call centers, etc.) and a
summary of locations included in the PCI DSS review.
Type of facility
Number of facilities
of this type Location(s) of facility (city, country)
Example: Retail outlets 3 Boston, MA, USA
Part 2d. Payment Application
Does the organization use one or more Payment Applications? Yes No
Provide the following information regarding the Payment Applications your organization uses:
Payment Application
Name
Version
Number
Application
Vendor
Is application
PA-DSS Listed?
PA-DSS Listing Expiry
date (if applicable)
Yes No

Part 2e. Description of Environment
Provide a high-level description of the environment covered by
this assessment.
For example:
Connections into and out of the cardholder data environment
(CDE).
Critical system components within the CDE, such as POS
devices, databases, web servers, etc., and any other
necessary payment components, as applicable.
Does your business use network segmentation to affect the scope of your PCI DSS
environment?
(Refer to Network Segmentation section of PCI DSS for guidance on network
segmentation)
Yes No
PCI DSS v3.2 SAQ A, Rev. 1.1 Section 1: Assessment Information January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 3
Part 2f. Third-Party Service Providers
Does your company use a Qualified Integrator & Reseller (QIR)?
If Yes:
Name of QIR Company:
QIR Individual Name:
Description of services provided by QIR:
Yes No
Does your company share cardholder data with any third-party service providers (for
example, Qualified Integrator & Resellers (QIR), gateways, payment processors, payment
service providers (PSP), web-hosting companies, airline booking agents, loyalty program
agents, etc.)?
Yes No
If Yes:
Name of service provider: Description of services provided:
Note: Requirement 12.8 applies to all entities in this list.
Part 2g. Eligibility to Complete SAQ A
Merchant certifies eligibility to complete this shortened version of the Self-Assessment Questionnaire
because, for this payment channel:
Merchant accepts only card-not-present (e-commerce or mail/telephone-order) transactions);
All processing of cardholder data is entirely outsourced to PCI DSS validated third-party service
providers;
Merchant does not electronically store, process, or transmit any cardholder data on merchant systems
or premises, but relies entirely on a third party(s) to handle all these functions;
Merchant has confirmed that all third party(s) handling storage, processing, and/or transmission of
cardholder data are PCI DSS compliant; and
Any cardholder data the merchant retains is on paper (for example, printed reports or receipts), and
these documents are not received electronically.
Additionally, for e-commerce channels:
All elements of the payment page(s) only and directly
from a PCI DSS validated third-party service provider(s).
2018-07-22

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 2: Self-Assessment Questionnaire January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 10
Appendix A: Additional PCI DSS Requirements
Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers
This appendix is not used for merchant assessments.
Appendix A2: Additional PCI DSS Requirements for Entities using SSL/early TLS
This appendix is not used for SAQ A merchant assessments
Appendix A3: Designated Entities Supplemental Validation (DESV)
This Appendix applies only to entities designated by a payment brand(s) or acquirer as requiring
additional validation of existing PCI DSS requirements. Entities required to validate to this Appendix
should use the DESV Supplemental Reporting Template and Supplemental Attestation of Compliance for
reporting, and consult with the applicable payment brand and/or acquirer for submission procedures.
PCI DSS v3.2 SAQ A, Rev. 1.1 Section 2: Self-Assessment Questionnaire January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 11
Appendix B: Compensating Controls Worksheet
YES with CCW
checked.
Note: Only companies that have undertaken a risk analysis and have legitimate technological or
documented business constraints can consider the use of compensating controls to achieve compliance.
Refer to Appendices B, C, and D of PCI DSS for information about compensating controls and guidance
on how to complete this worksheet.
Requirement Number and Definition:
Information Required Explanation

1. Constraints List constraints precluding compliance with the original requirement.
2. Objective Define the objective of the original control; identify the objective met by
the compensating control.
3. Identified Risk Identify any additional risk posed by the lack of the original control.
4. Definition of Compensating Controls Define the compensating controls and explain how they address the
objectives of the original control and the increased risk, if any.
5. Validation of Compensating Controls Define how the compensating controls were validated and tested.
6. Maintenance Define process and controls in place to
maintain compensating controls.

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 2: Self-Assessment Questionnaire January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 12
Appendix C: Explanation of Non-Applicability
If the (Not Applicable) column was checked in the questionnaire, use this worksheet to explain why
the related requirement is not applicable to your organization.
Requirement Reason Requirement is Not Applicable
Example:
3.4 Cardholder data is never stored electronically
Stripe
PCI DSS v3.2 SAQ A, Rev. 1.1 Section 3: Validation and Attestation Details January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 13
Section 3: Validation and Attestation Details
Part 3. PCI DSS Validation
This AOC is based on results noted in SAQ A (Section 2), dated (SAQ completion date).
Based on the results documented in the SAQ A noted above, the signatories identified in Parts 3b-3d, as
applicable, assert(s) the following compliance status for the entity identified in Part 2 of this document:
(check one):
Compliant: All sections of the PCI DSS SAQ are complete, all questions answered affirmatively,
resulting in an overall COMPLIANT rating; thereby (Merchant Company Name) has demonstrated full
compliance with the PCI DSS.
Non-Compliant: Not all sections of the PCI DSS SAQ are complete, or not all questions are answered
affirmatively, resulting in an overall NON-COMPLIANT rating, thereby (Merchant Company Name) has
not demonstrated full compliance with the PCI DSS.
Target Date for Compliance:
An entity submitting this form with a status of Non-Compliant may be required to complete the Action
Plan in Part 4 of this document. Check with your acquirer or the payment brand(s) before completing
Part 4.
Compliant but with Legal exception:
restriction that prevents the requirement from being met. This option requires additional review from
acquirer or payment brand.
If checked, complete the following:
Affected Requirement Details of how legal constraint prevents requirement being met
Part 3a. Acknowledgement of Status
Signatory(s) confirms:
(Check all that apply)
PCI DSS Self-Assessment Questionnaire A, Version (version of SAQ), was completed according to the
instructions therein.
All information within the above-referenced SAQ and in this attestation fairly represents the results of
my assessment in all material respects.
I have confirmed with my payment application vendor that my payment system does not store sensitive
authentication data after authorization.
I have read the PCI DSS and I recognize that I must maintain PCI DSS compliance, as applicable to
my environment, at all times.
If my environment changes, I recognize I must reassess my environment and implement any additional
PCI DSS requirements that apply.
PCI DSS v3.2 SAQ A, Rev. 1.1 Section 3: Validation and Attestation Details January 2017
© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 15
Part 4. Action Plan for Non-Compliant Requirements
Select the appropriate t for each requirement. If you
o may be required to provide the date your Company expects to be
compliant with the requirement and a brief description of the actions being taken to meet the requirement.
Check with your acquirer or the payment brand(s) before completing Part 4.
PCI DSS
Requirement* Description of Requirement
Compliant to PCI
DSS Requirements
(Select One)
Remediation Date and Actions
(If selected for any
Requirement)
YES NO
2 Do not use vendor-supplied
defaults for system passwords and
other security parameters
8 Identify and authenticate access to
system components
9 Restrict physical access to
cardholder data
12
Maintain a policy that addresses
information security for all
personnel

* PCI DSS Requirements indicated here refer to the questions in Section 2 of the SAQ.

DOWNLOAD MAXPANDA’S PCI / DATA COMPLIANCE DOCS – pci-compliance-maxpanda

zapier maxpanda api

Integrated CRM & Accounting

­Maxpanda mAPI Integration – Getting started with Zapier

Integrate your various applications to Maxpanda CMMS using Zapier. Zapier is a platform which connects apps with each other without having to write any computer code.

To learn more about Zapier read this – short article.

To get started with Maxpanda App on Zapier – click here.

DOWNLOAD THE FREE PDF FILE FOR DISTRIBUTION: Maxpanda-Zapier

You can use Maxpanda CMMS + any Zapier integration as long as you have a Maxpanda “Enhanced, Standard, Pro or Enterprise” subscription plan.  Compare your plan that supports Auto Sync Client Data hereIf your app is supported in Zapier you may integrate with Maxpanda CMMS. Zapier supports thousands of apps. Review supported apps online at https://zapier.com/apps

Here are few use cases where you can integrate Maxpanda with apps.

  1. When a new customer invoice is created in Maxpanda, a Zapier integration can directly create an invoice in your accounting software (If it is supported in Zapier). Quickbooks , Xero, Freshbooks, Zoho Books are few supported accounting packages. There are thousands of supported accounting apps.
  2. When a new customer is created in your CRM software or accounting software, Zappier can create that customer in your Maxpanda CMMS account automatically.
  3. Vendor Management: A vendor can also automatically be created in Maxpanda CMMS if such vendor gets created in your ERP or CRM software.

Getting Started:

  • If you are on supported subscription plan, login with company admin access.
  • Go to profile page and select enable all Users access to mApi & to the user you want to access integration.
  • Please note: The transactions completed using API / Integration will be completed through the individual user.

After enabling access – logout & login again with the User who has mApi access. User should now see an integration menu at the top right dropdown.

Select the Integration Menu: Here you’ll see a Generate Key button under Application & mAPI.

Press the “Generate” key button to generate a Private Key for your Zapier integration.

Please note: Do not regenerate key more than once. If you regenerate your key you have to reconnect your Zapier integrations with the new key.

Let’s start creating an integration.

Use Case: “Integrating with QuickBooks” – If a new Customer Invoice gets created in Maxpanda then it also gets created in QuickBooks. This can be done with any supported accounting app once your Maxpanda account is integrated with Zappier.

Create a Zapier account if you don’t have one.

Use this link to access Maxpanda App on Zapier. You can also search it in Zapier app directory.

zapier maxpanda api

Click Accept & Build Zap button on this invitation page.

Click on Make a Zap.

Now we want to push all new customer invoices to QuickBooks

invoices to QuickBooks

Provide a suitable name to your new Zap (a Zap is an integration configuration between Zapier, Maxpanda and any other app).

Then select Maxpanda CMMS as your Trigger App.

Under trigger click choose app & select Maxpanda.

Selecting a trigger app: In this use case let’s select a trigger when a new Customer Invoice gets created.

Click Save & Continue.

 Customer Invoice

Click connect an Account button. It will ask you for your Api Key. Enter the key generated under the Application & mAPI section of Maxpanda.

zapier maxpanda api

After your key is entered, press test button & verify that your test is successful.

zapier maxpanda api

At this point Maxpanda CMMS should be connected to Zapier

At this point Maxpanda CMMS should be connected to Zapier.

Zapier will now fetch a single invoice to ensure all invoice fields are valid. Make sure you have at least one customer invoice created in Maxpanda CMMS for this test to be successful.

Successful test should show only one fetched invoice.

api success

In this next step we have to connect with your target application (Quickbooks, Freshbooks etc…). In this case, we are connecting to QuickBooks accounting software.

Step 2: Choose your accounting app under action

Select QuickBooks for integration

Select QuickBooks for integration

Now we want to create a new invoice in QuickBooks when an invoice gets created in Maxpanda CMMS.

Select Create Invoice Action under step 2, Choose Action.

You must next connect to your QuickBooks account.

Click on “Connect an Account“

You will be asked for QuickBooks login & Authorization for API access.

zapier maxpanda api

Click on “Connect”.

zapier maxpanda api

Test connectivity using the “Test button”.

zapier maxpanda api

Click Save & Continue.

This next step is extremely important where you will be required to map important fields from your Maxpanda invoice data to QuickBooks.

zapier maxpanda api

At this point you’ll want to search your customers in QuickBooks OR create new customers if you do not have any customers.

Click Add a search step under customer field, this will add a new step in your Zapier workflow.

zapier maxpanda api

We now ask Zapier to search your customers in QuickBooks by using email. (You can also use other unique identifier such as phone number etc…).

Now map Maxpanda email fields in the dropdown to search value.

zapier maxpanda api

Creating a new Customer in QuickBooks if customer does not exists:

So, click on “Create QuickBooks Online Customer if it doesn’t exist yet?”

Map create customer fields from Maxpanda to your QuickBooks fields.

zapier maxpanda api

zapier maxpanda api

Now you can create a customer using fetched data.

zapier maxpanda api

This step will try to create a new customer in QuickBooks.

zapier maxpanda api

You may also login to QuickBooks to review if customer is created correctly.

Final step for complete integration is to create a template for invoice mapping.

Go to setup template for step 3 (Create Invoice)

zapier maxpanda api

Begin mapping desired fields for the QuickBooks Invoice with the Maxpanda invoice module. You must select fields from step one “New Customer invoice”.

zapier maxpanda api

zapier maxpanda api

zapier maxpanda api

You need to map each line item in invoice as shown below.

zapier maxpanda api

For Product / Service invoicing, your accounting software (QuickBooks) & Maxpanda have these entries pre-installed.

Example: All Invoice Item Types in Maxpanda should be present in QuickBooks

zapier maxpanda api

Values from QuickBooks

zapier maxpanda api

After reviewing this, map all fields to each line item. Once you’ve mapped all relevant fields, click continue – this will send a test invoice to QuickBooks.

zapier maxpanda api

zapier maxpanda api

Click send test to QuickBooks Online

zapier maxpanda api

Click “finish” once test is successful. You may also login to QuickBooks and verify if the invoice is successfully created.

At this point your Zap is ready. Turn it on once you’re ready begin using your brand new Zap.

Using preventive maintenance software

Asset Metering Setup

Meter Reading

  1. Go to COMPANY menu then select METERING TYPES to define the type of meters to run on your ASSETS such as hours/levels/temp/odometer readings etc.
  2. Edit an existing Maxpanda METER (we provide 6 templates) type or create a new one to fit your needs.
  3. Assign it to your Site or Multi Sites (see the picture).
  4. Edit an asset and assign 1 or more metering types to it (your almost done).
  5. The HOURS example (in the picture) has a trigger set for every 80 hrs. Every 80 hours entered by staff on this asset, a new work order is generated.
  6. Feel free to print the qrcode of your asset. Using our freemobile app (GoMAX CMMS Assistant) staff are able to scan the asset’s QR Code, update the hours and save, using their smartphone.
  7. Each trigger (80 hours) will generate work orders for supervisors/editors/admins to assign to staff for completion.

Auto-pull PM template data into a Metering Work Order

NOTE: This feature uses PM TEMPLATES not PM’s.

1. Create a new PM template
2. Open it and click the checkbox to ACCESS IN METERING
3. Save

1. Add your desired METER reading type to any asset
2. Select your PM template from the dropdown menu
3. Save