Tablet showing a compliance checklist with ISO 27001, LGPD and PCI DSS
Short answer

The 10 IT documents a hotel needs are: an inventory of systems and equipment, a vendor and contract list, a network diagram, admin accounts and domain ownership, an access matrix by role, a backup policy with restore evidence, a contingency plan, an incident response plan and incident register, the LGPD record of processing activities (art. 37) and the PCI DSS documentation that fits how the hotel takes cards (SAQ or assessment report, AOC, card data flow and vendor responsibilities).

A hotel's IT documents tend to live in the head of whoever has been there longest, or in a vendor's inbox. The problem shows up when someone asks for one: in due diligence the buyer of the hotel wants the contract list, and a new network vendor wants the diagram before touching anything.

The 10 documents

1. Inventory of systems and equipment

The list of computers, servers, network equipment, systems and cloud subscriptions (PMS, POS, booking engine, channel manager, electronic locks, guest Wi-Fi, CCTV), with location, owner and the date each item loses manufacturer support. Include the PMS integrations and who holds the credentials for each one. Almost every other document builds on it. Update it at every purchase, replacement or retirement, and check the whole list once a year.

2. Vendor and contract list

Who supplies what, the support and escalation contacts, support hours, the SLA, the renewal date, the notice period for not renewing and how the hotel exports its data if it changes vendor. It covers the PMS, the payment processor, the internet provider, the channel manager and, if there is one, the group's or brand's IT provider. A missed 90-day notice can lock the hotel in for another contract cycle. See hotel IT vendor management.

3. Network diagram

A simple drawing of how the network is split: guests, staff, payments, cameras, third-party systems. It shows whether guest Wi-Fi is separated from the POS, which is the first question from a new network vendor and from a PCI DSS assessment (requirement 1.2.3). The path card data takes between terminal, PMS, booking engine and gateway is a separate drawing, the one in document 10. Update it at every network change.

4. Admin accounts, domain and password vault

Who is admin of each system (PMS, booking engine, OTA extranets, door locks, email and cloud), whose name the domain and the corporate email admin account are in, and where the admin passwords are kept. Keep the passwords in a password vault with MFA and an access log, open only to the people who need them. Document at least two authorised, tested ways to recover access in an emergency, so that no account depends on one employee or one vendor.

5. Access matrix by role

Which systems each role uses, and with which profile: front desk, reservations, finance, housekeeping, management, plus vendor accounts and emergency accounts. It is what lets you revoke everything on the day someone leaves. Review it twice a year and at every hire, exit or change of role. See the access to revoke when an employee leaves.

6. Backup policy and restore evidence

What is backed up, how often, where the copy outside the main environment sits, how much data the hotel can afford to lose and how long each critical system can be down. For cloud systems, such as a PMS hosted by the vendor, note who runs the backup, which data the hotel can export, how to request a restore and how fast the contract guarantees it. The policy needs the evidence with it: the report of the last restore test, with the date, how long it took and whether the system worked afterwards. When the hotel cannot test on its own, ask the vendor for that evidence.

7. Contingency plan

How the front desk works if the PMS, the internet or the door lock system goes down: where the arrivals list is, how to record a provisional check-in, which payment methods the front desk may use and whom to call. Do not write card numbers or security codes on paper, in a spreadsheet or on WhatsApp: PCI DSS forbids keeping the security code after authorisation, even encrypted. When the system is back, someone enters everything done by hand into the PMS. Test it twice a year, before the high seasons. See the IT contingency plan.

8. Incident response plan and incident register

Who decides what in a security incident, who talks to guests, to the ANPD and to the insurer, and which evidence to keep. The register records each incident involving personal data: the date the hotel became aware of it, what happened, which data and how many people were affected, the risk assessment and the measures taken. ANPD Resolution 15/2024 requires the controller to keep it for at least five years, including incidents that were not reported. See what to do in the first 48 hours of a breach.

9. Record of processing activities (LGPD)

Article 37 of the LGPD requires the controller and the processor to keep a record of their personal data processing: which data the hotel collects (FNRH guest registration, CCTV, Wi-Fi sign-up, marketing, staff data), what for, on which legal basis, whom it shares it with and how long it keeps it. ANPD Resolution 2/2022 allows a simplified record for small processing agents, when the hotel meets the resolution's criteria (size, group revenue and no high-risk processing), and the ANPD publishes a template for it (in Portuguese). Review it once a year and whenever a system, a purpose or a vendor changes. See the LGPD for hotels.

10. PCI DSS documentation

The set depends on how the hotel takes cards: the SAQ or assessment report and the attestation of compliance (AOC), when the acquirer requires them, the card data flow diagram (requirement 1.2.4), the list of vendors that affect that data, each vendor's compliance status, checked at least every 12 months (requirement 12.8.4), and the matrix showing which requirements each vendor handles and which stay with the hotel (requirement 12.8.5). When payments are outsourced, monitoring the vendors still falls to the hotel. The acquirer decides when and how the hotel validates. See PCI DSS for hotels.

Who asks for each document

The review frequencies are suggestions; a major change at the hotel also calls for a review. The annual IT calendar spreads those reviews across the year.

DocumentWho tends to ask for itSuggested review
InventoryBuyer, new vendor, insurerAt every change, with a yearly check
Vendors and contractsManagement, buyerBefore each renewal
Network diagramNew network vendor, PCI DSS assessmentAt every change
Admins and domainBuyer, new vendorAt every exit or vendor change
Access matrixAudit, PCI DSS assessmentTwice a year and at every staff change
Backup and restoreInsurer, buyerYearly, with a test
Contingency planManagement, insurerTwice a year, with an exercise
Incident response and registerANPD, insurerYearly and after each incident
Record of processing (LGPD)ANPD, buyerYearly and at every change of system or purpose
PCI DSS (SAQ, AOC, data flow, 12.8)AcquirerOn the acquirer's date; vendors every 12 months

Where to keep them

Keep the documents outside the systems they describe. A contingency plan that only exists on the hotel's server won't open when the server is down, and a ransomware response plan saved on the encrypted network is no use at all. Keep the working version in a cloud service with MFA and version history, and an emergency copy that two people can open even when email or the main login is down. Only the contingency plan sits printed at the front desk; passwords and network diagrams stay off the counter.

Where to start

Start with the inventory and the vendor list: the other documents depend on them. Then the admin accounts and the domain, because losing access to one of them is the hardest problem to undo. The LGPD and PCI DSS documents come after, with the inventory in hand. For each document, note the owner, the date of the last review and how it was checked: the network diagram, for example, compared against the network as installed.

Next steps

HotelTI's IT assessment surveys what already exists, maps vendors and contracts and delivers a report with the gaps prioritised. Keeping the documents up to date through the year is part of IT management. HotelTI is not a QSA and does not issue certificates. We do not resell software or have agreements with specific vendors. Talk to our team.

Sources

  • Presidência da República, Lei 13.709/2018, General Data Protection Law (LGPD), art. 37, planalto.gov.br
  • ANPD, Resolution CD/ANPD 2, LGPD regulation for small processing agents (January 2022), in.gov.br
  • ANPD, Resolution CD/ANPD 15, Security Incident Reporting Regulation (April 2024), in.gov.br
  • PCI Security Standards Council, PCI DSS v4.0.1, requirements 1.2.3, 1.2.4, 3.3.1, 12.8.4 and 12.8.5, pcisecuritystandards.org
  • PCI Security Standards Council, How do I determine whether my business would be required to conduct an independent assessment or a self-assessment? (FAQ 1126), pcisecuritystandards.org
  • ANPD, ANPD divulga modelo de registro simplificado de operações com dados pessoais para Agentes de Tratamento de Pequeno Porte (ATPP) (in Portuguese), gov.br/anpd

IT assessment

What already exists, what is missing and what to do first.

View service
  • Report with prioritised findings
  • Map of vendors and contracts
  • Recommendations and initial roadmap
  • Board presentation
Does a small hotel need all 10?

Yes, in short versions sized to the operation. At an inn, the inventory can be a spreadsheet, the network diagram one page and the record of processing the simplified version under ANPD Resolution 2/2022, if the hotel qualifies as a small processing agent. The PCI DSS documentation depends on how the hotel takes cards. Each document needs to exist, have an owner and be up to date.

Where should the documents be kept?

Outside the systems they describe: the working version in a cloud service with MFA, an emergency copy that opens even without the main login, and the contingency plan printed at the front desk.

Shouldn't the IT vendor have these documents?

The vendor can prepare several, such as the inventory and the network diagram, but the hotel needs its own copy. If the contract ends or the vendor disappears, the documents have to stay with the hotel.

Does HotelTI prepare these documents?

The IT assessment surveys what exists and what is missing. Under IT management, HotelTI keeps the governance documents up to date through the year and asks the vendors for the ones that fall to them. HotelTI is not a QSA and does not issue certificates.

Are your hotel's IT documents up to date?

Talk to our team about an IT assessment.