In short
On 12 November 2026 the Italian Garante published a Black Friday guide on scam websites, fake delivery notifications and payments.
For online sellers the main risks are brand phishing, account takeover, website unavailability and suppliers.
Before the peak: patches, MFA on admin accounts, web application testing, payment provider requirements and a restore test.
SPF, DKIM and DMARC, a clear notice to customers and a prepared customer service team help people spot fake messages.
In a personal data breach, notify the supervisory authority within 72 hours where required and inform customers if the risk is high.
On 12 November 2026 the Italian data protection authority (Garante per la protezione dei dati personali) published, in newsletter no. 556, a guide to safer shopping ahead of Black Friday, which this year falls on Friday 27 November. The advice covers scam websites, fake delivery notifications, online payments, security updates and two-factor authentication.
The guide is written for consumers, but every tip has a flip side for businesses that sell online. If fraudsters imitate shops' websites and messages, your brand is the bait. In this guide you will find a security checklist for B2C and B2B e-commerce and for employees: what to do before, during and after the year-end peaks, with official sources and the GDPR obligations in the event of a personal data breach.
What does the Garante's guide say and why does it matter to online sellers?
The guide describes the risks from the buyer's side: offers that are too good to be true, fake websites, messages about orders and deliveries, payments. Read from the seller's side, it becomes a list of things customers will look for on your website and in your messages to decide whether they can trust you.
Scam websites and fake delivery notifications: your brand as bait
The Garante advises checking that the website address matches the company name and contains no unusual letters or characters, even when it looks like the genuine one. It also recommends reaching the website by typing the address rather than clicking links received by email, text message or social media, and reminds readers that even a professional-looking website can be fraudulent.
On deliveries the guide is explicit: fake delivery notifications, which mention order updates, delivery problems or parcels to collect, are a danger that grows during the Black Friday period and can deceive even people who really are waiting for a parcel. The advice is to check on the official website or app of the seller or courier, without using the links in the message. The Italian Postal Police (Polizia Postale), in its page on phishing, also lists websites that require registration, such as e-commerce sites, among the senders that are imitated, and fake parcel delivery notices among infected attachments.
For a business, this means customers will check your official channels: if they are clear and consistent, checking is easy.
Payments, updates and two-factor authentication
The Garante suggests that consumers prefer prepaid cards or systems that avoid sharing bank details with the seller, turn on transaction alerts and check for an encrypted connection, while remembering that the padlock alone does not guarantee the website is trustworthy. It ends with two recommendations that apply equally to businesses: install security updates promptly and turn on two-factor authentication for accounts.
Which risks grow for an e-commerce business during peak periods?
During peaks, traffic, orders and messages grow, and with them the opportunities for those who want to exploit them. You do not need figures to see it: the Garante itself writes that fake delivery notifications increase during the Black Friday period. There are four main risks for sellers.
Phishing that imitates your brand: emails, text messages and other messages that use your name to steal customers' credentials or payment details, or websites with addresses similar to yours.
Account takeover: logins with credentials stolen elsewhere, both to customer accounts and, more dangerously, to the platform's administrative accounts.
Service unavailability: peaks of legitimate traffic, attacks aimed at overwhelming the website, last-minute updates.
Suppliers and external components: plugins, modules, third-party scripts, agencies and suppliers with access to the admin panel.
Credential stuffing and account takeover
ENISA and CERT-EU, in a joint publication from February 2022, explain that threat actors often compromise organisations through credential stuffing: they try username and password pairs leaked from breaches of other services, exploiting the fact that many people reuse the same credentials. Their recommendations are multi-factor authentication for remotely accessible services, no password reuse and, where possible, a corporate password manager.
For an e-commerce business the risk is twofold. Customer accounts can be used for fraudulent orders or to steal data; administrative accounts can give access to orders, data and payment settings. That is why the first measure in the checklist concerns access.
Employees, the first target of order-themed messages
During peaks, employees also receive more messages about orders, returns and deliveries, with less time to check them. A fake email asking them to log in to the admin panel, open an "invoice" or, in B2B, change a customer's or supplier's bank details can arrive just when the warehouse and customer service are under pressure. ENISA and CERT-EU recommend regular awareness sessions on the most common phishing techniques: a short reminder before the peaks is the right moment.
What to do before the peak: the operational checklist
Before the peak it pays to finish your security work and freeze non-essential changes. The weeks before Black Friday are the time to update, test and check; the peak days are the time to touch as little as possible.
Platform, plugins and suppliers up to date
Update the platform, plugins, modules and server components with the available security patches, prioritising the most serious known vulnerabilities, as ENISA and CERT-EU recommend. Do it early and in a test environment.
Use the update to carry out an inventory of components: remove plugins and modules you no longer use, check that the remaining ones are still maintained by their developers, and check which third-party scripts run on your checkout pages. Then move on to suppliers: who has access to the admin panel, with which permissions, and until when. ENISA and CERT-EU recommend tightly controlling third-party access to systems, because a compromised supplier can become the way in. For a structured method you can follow the guide on ISO supplier evaluation.
MFA on administrative accounts and protection of customer accounts
Turn on multi-factor authentication for all administrative accounts: the e-commerce admin panel, hosting, domain and DNS, email, order management system and your account with the payment provider. ENISA and CERT-EU suggest, where possible, preferring phishing-resistant factors such as security keys over codes sent by text message. Remove shared accounts and those of former staff, and change all default credentials.
For customer accounts, discuss with your developers measures against automated login attempts: limits on repeated attempts, extra checks on unusual logins, alerts to customers about logins from new devices, and the option to turn on two-factor authentication. Calibrate them so as not to block legitimate customers.
Security testing of the web application
Article 32 of the GDPR requires, among security measures, a process for regularly testing and evaluating the effectiveness of the measures in place. For an e-commerce business the most useful test is on the web application: registration, login, password recovery, basket, checkout, customer area and admin panel.
A web application penetration test (WAPT) simulates an attacker's behaviour and gives you the vulnerabilities to fix in order of severity. It should be done well ahead of the peak, so that you have time to resolve the issues and run a final check. If you are not sure which test you need, the guide on penetration tests and vulnerability assessments explains the differences.
Payments: follow your provider's requirements
Card payment handling has specific security requirements, which your payment provider sets out according to how you have integrated the service. Check them now: which integration method you use, which periodic checks are required of you, who carried them out last time and when.
In general, the less payment data passes through your systems, the lower your exposure. Check that the website does not store unnecessary card data and that the provider's alerts on unusual transactions reach someone, including on bank holidays.
Backups, capacity and continuity
ENISA and CERT-EU recommend the 3-2-1 rule: three complete copies of data, two stored locally on different types of media and at least one off-site, with explicit recovery time and recovery point objectives, controlled and logged access to backups, and restore procedures that are documented and tested regularly. Article 32 of the GDPR, for its part, mentions the ability to restore the availability of and access to personal data in a timely manner in the event of an incident.
Before the peak, run a real restore test, not just a check that the backup has started. Check with your hosting or cloud provider the capacity planned for the expected traffic and the protections against attacks aimed at overwhelming the website, among those recommended by ENISA and CERT-EU. Decide who makes decisions and how customers are informed if the website goes down. The guide on the business continuity plan for SMEs helps you set it up.
How do you protect customers from phishing that imitates your brand?
You cannot stop a fraudster from using your name, but you can make it easier to spot.
Email authentication and lookalike domains
Italy's National Cybersecurity Agency (ACN), in its April 2026 guidelines on email configuration, explains that sender authentication helps counter spoofing and phishing and describes the three protocols to use together: SPF, DKIM and DMARC. Configuring them on the domain from which you send order confirmations, delivery notifications and newsletters makes it harder to send fake emails that appear to come from you.
CSIRT Italia, in a February 2026 bulletin, reported attackers' use of lookalike domains in frauds that compromise business email. Consider monitoring domains similar to yours and, for the most obvious ones, registering them in advance. Always use the same domains and senders for customer communications, so that a different address stands out.
What to tell customers before Black Friday
A short notice, on the website and in communications you already plan to send, is more useful than an alarm. Take the Garante's advice and turn it into commitments customers can check: list what your company will never ask for (passwords, codes received by text message, full card details, payments outside the website), state your official channels and invite customers to check order status only from their customer area or the app.
Keep the same style in genuine notifications: no links to login pages unless they are needed, consistent senders, and order information that a fraudster is unlikely to know.
Customer service as an early warning system
Prepare customer service to receive reports of suspicious messages and to reply with a simple script: thank the customer, ask them not to click, ask them to forward the message to a dedicated address, and never ask for passwords or codes. Reports should be logged and passed on to whoever manages security: many similar reports within a few hours may point to a campaign under way or, in some cases, a breach not yet discovered.
What to do during the peak?
During the peak the goal is to spot problems early and decide quickly.
Clear on-call rotas: who monitors the website, who can block an account, who talks to the hosting provider and payment provider, including at weekends.
Changes kept to a minimum: no new plugins or non-urgent updates during the peak days, except critical security patches assessed case by case.
Login monitoring: spikes in failed logins, administrative logins from unusual locations or devices, unusual orders, changes to payment pages.
Contacts ready: suppliers, hosting, consultants, DPO and, if you are an entity in scope of NIS2, the CSIRT channels of your country. ENISA and CERT-EU recommend having procedures to contact your CSIRT swiftly.
Checks on bank detail changes: in B2B, any request to change bank details is verified with a phone call to a number you already know, not by replying to the email.
Remind employees that, on the busiest days, a minute spent checking is worth more than an instant reply: a message demanding urgency, credentials or payments outside the usual procedure should be reported, not acted on.
What to do if something goes wrong: incidents and GDPR obligations
If you suspect an incident, activate your response plan: contain, preserve evidence, assess the impact, decide on communications.
When a breach must be notified to the supervisory authority
If the incident involves personal data, for example customer accounts, addresses or order data, it is a personal data breach. Article 33 of the GDPR requires notification to the supervisory authority without undue delay and, where feasible, within 72 hours of the controller becoming aware of it, unless the breach is unlikely to result in a risk to people's rights and freedoms. In Italy notification is made through the Garante's online procedure, which also offers a self-assessment tool; elsewhere, follow your competent authority's procedure.
If the breach occurs at a supplier that processes data on your behalf, such as the hosting provider or an external service, Article 33 requires the processor to inform the controller without undue delay. Check now that your supplier contracts provide for this and that suppliers know whom to contact. Whatever the outcome, every breach must be documented: the facts, its effects and the remedial action taken.
When to inform customers
Article 34 requires communication to data subjects when the breach is likely to result in a high risk to their rights and freedoms, in clear and plain language. The assessment must be made case by case with your DPO or privacy adviser: this is not legal advice, just a reminder of the steps. Timings and content are explained in the guide on what to do in the first 72 hours after a data breach.
If your company is in scope of NIS2, also check the notification obligations for significant incidents, which come on top of those under the GDPR. The guide on ISO 27001 and NIS2 explains how the two fit together.
What to do after the peak?
After the peak, carry out a calm review within a few weeks, while the details are still fresh.
Clean-up and review
Remove temporary accounts, permissions granted to suppliers for the period and any emergency configurations still active. Review the phishing reports received by customer service and the anomalies picked up by monitoring. Update the component inventory and schedule the patches postponed during the change freeze.
If there were incidents, even minor ones, record what happened and the corrective actions you decided on. This is the basis for improvement and, if you are an obliged entity, part of the evidence to show during an inspection.
From checklist to management system
A seasonal checklist works, but peaks come back every year: sales, holidays, product launches. An information security management system based on ISO/IEC 27001 turns the same activities into repeatable processes: risk assessment, supplier and vulnerability management, backups and continuity, incident management, training and periodic reviews. For B2B sellers it is also an answer to customer security questionnaires, which increasingly ask for evidence on these topics. For the full picture, see the complete guide to ISO 27001.
How Complaion helps you with information security and data protection
Complaion supports businesses with information security and data protection: ISO 27001 certification, NIS2 compliance, GDPR compliance including an outsourced DPO service, and web application penetration testing.
A dedicated Lead Auditor works with your company, analyses your starting point and proposes the most suitable path. The platform collects evidence, manages documents and procedures, keeps track of deadlines and prepares you for the audit, so that security activities do not depend on one person's memory.
More than 1,000 clients have already chosen Complaion. If you want to know where to start, contact us.
Frequently asked questions on e-commerce security for Black Friday
Does the Garante's Black Friday guide also concern businesses?
It is aimed at consumers, but every tip has a counterpart for sellers: customers will check the website address, delivery notifications and official channels. Making these clear and consistent, and protecting your own accounts with updates and multi-factor authentication, is the way to help them.
How long before Black Friday should you run a security test?
Early enough to fix the vulnerabilities found and run a final check before the peak. Article 32 of the GDPR in any case requires measures to be tested and evaluated regularly, not just once.
Should multi-factor authentication also be turned on for customers?
For administrative accounts it is a basic measure. For customers it is best to offer it as an option and combine it with other protections against automated logins, calibrated so as not to block genuine shoppers. ENISA and CERT-EU recommend multi-factor authentication for remotely accessible services.
What should I do if someone creates a fake website using my brand?
Collect evidence, warn customers through your official channels and report the case to the police (in Italy, the Polizia Postale) and, if necessary, to the registrar or host of the fake website. Assess with a lawyer the steps to protect your brand.
Is a successful credential stuffing attack a data breach?
If an attacker accesses customer accounts containing personal data, it may be. The assessment must be made case by case with your DPO: if the breach poses a risk to people, it must be notified to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it; in any case it must be documented.
Is the e-commerce provider responsible for the security of my website?
It depends on the contract and the service, but GDPR obligations towards customers lie with the data controller, which is normally your company. A provider processing data on your behalf must inform you of a breach without undue delay: check that the contract provides for this and that the security measures are clear.












