Gas station cybersecurity due diligence should map the systems, records, people, and vendors the buyer needs. Check who controls accounts and recovery settings, then review known incidents and provider duties. Plan the handoff with authorized support. Test the buyer’s access before removing old users, and keep records required by law or for running the store.
Which systems should be on the buyer’s inventory?
List each system that supports trading, reporting, payments, or access to private records. A station can depend on separate POS, back-office, fuel-ordering, accounting, camera, payroll, and email services. Identify the actual setup rather than treating the register as the whole technology package.
For each item, record who owns the hardware, who holds the contract, and who controls the account. These can be different people or companies. Note where records are stored and how the buyer expects to retrieve them. An equipment list can show a computer without establishing any right to use the software installed on it.
Use the buyer diligence checklist to place this review beside financial, property, and environmental work. Give each missing item a named contact and deadline. A system needed for the first shift deserves earlier attention than a discretionary tool the buyer can replace later.
What data should the buyer inspect without collecting too much?
Inspect the information needed to assess the transaction while limiting exposure of private records. The FTC’s personal-information guide recommends mapping what a business holds and who can access it. That principle applies to physical files, devices, cloud services, and vendor-held data.
Ask what payroll, customer, payment, camera, and other private records the store keeps before requesting copies. Check whether a summary or a sample with private details removed will answer the question. Have counsel set limits on who sees and shares those records. Some may contain private data, deal terms, or evidence that must be kept for a dispute.
Keep a distinction between proof of financial results and unnecessary raw personal data. The P&L review guide explains reconciliation of business totals. Full card details or employee identity documents generally are not needed to understand whether sales totals agree with bank records.
Track the files shared and the people allowed to use them. Agree on storage, return, retention, and disposal through the deal’s approved process. Do not delete records simply because they seem old: tax, employment, contract, or dispute obligations may require preservation beyond the transaction.
How should vendor responsibilities be checked?
Request written agreements and a clear description of what each provider does. A vendor may host data, maintain software, manage networks, or supply remote support. Knowing its name is not enough to establish which risks it handles or which tasks remain with the store.
The PCI provider FAQ explains that customers must oversee relevant third-party relationships under Requirement 12.8. It addresses agreements, allocation of duties, and monitoring compliance status at least annually. It does not say that every provider must hold validation solely for the customer to meet that requirement.
Ask the provider and the organization managing the merchant’s compliance program which evidence applies to the actual service. Separate a sales claim from dated supporting records. A general statement that the product is secure does not describe who updates it, reviews access, or responds to an incident at this site.
Review change-of-owner instructions before assuming the contract or account can transfer. Mark consent, new underwriting, replacement agreements, and setup fees as separate tasks where applicable. A technical service can remain available while the buyer still lacks the contractual right to use it.
Who controls recovery settings and privileged access?
Identify the people who can add users, change payment settings, restore accounts, or authorize vendor access. These powers can matter more than a cashier login. A buyer may enter the system successfully while the seller’s personal email still controls the password reset.
| Control | Evidence to review | Handoff question |
|---|---|---|
| Administrator role | Named users and assigned permissions | Can the buyer manage approved accounts? |
| Recovery method | Provider-confirmed recovery contact settings | Who can restore access after a lockout? |
| Remote support | Vendor access scope and approved contacts | Which outside users remain necessary? |
| Account ownership | Contract holder and transfer instructions | Is provider consent or a new account required? |
Build the change plan with the seller and authorized provider. Establish buyer-controlled roles and recovery methods through the service’s own process. Avoid relying on informal use of a seller’s personal account, which may mix business records with unrelated private information and create fragile access.
Do not remove all old access at once without checking dependencies. Scheduled reports, backups, integrations, and support tools can depend on accounts that appear inactive. Have qualified support identify those links and sequence the changes so the handoff does not interrupt essential operations.
What security evidence is useful before signing?
Ask for dated records that show how access, updates, backups, and incidents are managed. The FTC’s small-business cybersecurity guidance discusses these controls and multifactor authentication. A buyer should use the guidance to ask focused questions, rather than claim that a completed checklist certifies security.
Request the latest service reports, open support tickets, backup schedules, and documented incidents relevant to the acquired systems. Ask who reviews alerts and who responds when a problem occurs. A vendor invoice may establish that support was purchased, but it does not prove every promised task was performed.
Review known interruptions with their dates, affected services, response, and unresolved work. Distinguish a routine outage from a confirmed compromise and from an unexplained error. Do not label a seller’s system breached without evidence. Counsel can manage sensitive incident information and assess disclosure or claim issues.
If deeper testing is needed, agree on authority and scope before work begins. A qualified reviewer should know which assets belong to the seller, provider, landlord, or another party. A buyer’s offer does not grant permission to probe live systems or change settings that could affect trading.
How should the closing handoff be sequenced?
Use a coordinated sequence that preserves records, establishes buyer control, verifies required functions, and then removes obsolete access. Set the timing with the people responsible for operations and vendor support. Include a response plan if an account transfer takes longer than expected.
Start by confirming contracts, the authorized contacts, and records needed after closing. Next establish the buyer’s approved accounts and recovery settings. Have the provider confirm how to test required functions without using unauthorized payment transactions or changing production settings outside the agreed scope.
Record the results for report access, approved administrative duties, and essential service connections. Then revoke or limit seller and former-worker access as agreed, retaining only documented support arrangements that remain necessary. Use an approved secure method for secrets that must move; do not put passwords in the general sales packet.
The first-ninety-days guide connects this handoff to daily reporting and opening balances. Keep technology duties on that operating schedule, with a responsible person and evidence of completion. A task described as “vendor will handle it” still needs an owner who checks the result.
How should open issues affect the purchase decision?
Assess each gap by its operating impact, required remedy, cost, and timing. Some issues can be resolved before possession; others may require new hardware, a provider agreement, or further review. Avoid a blanket price adjustment that treats every incomplete record as the same risk.
Get written quotes when a fix requires paid work. Separate setup from monthly fees and support, and show any time the store may be unable to trade. Do not count a full year of savings from a system that must be replaced at once. Check when the new setup can start and what the buyer must pay until then.
Have counsel and the lender review major duties that remain unclear. The contract may need required proof, conditions to close, or terms that assign specific risks. Check insurance on its own terms: policy wording, exclusions, dates, and the insurer’s approval matter. Do not assume a policy covers every cyber loss just because that word appears in its name.
Return to the buyer planning hub when deciding whether the supported operating case still fits the purchase. The goal is documented control of necessary systems, with known duties and open questions addressed. Keep the handoff record available after closing so the buyer can check access again as staff and vendors change.