November sales put your login and checkout pages under heavier, more varied use than a normal week. This article is a practical seven-point checklist you can work through before the campaign week. It does not claim which flaws are most common in Turkish stores, it quotes no invented percentages, and it is not a guarantee of security. The aim is to put frequently skipped points in the payment and membership flow in a useful order. For a broader testing frame, see the e-commerce security testing article.

1. Admin panel and staff accounts

During a campaign, more accounts can issue coupons, change stock or handle orders. Each staff member should have their own account, shared passwords should not circulate, and access for someone who has left should be closed the same day. Multi-factor authentication should be on for administrator and accounting accounts. The OWASP Authentication Cheat Sheet treats multi-factor authentication as one of the strongest defences against password-based attacks.

You do not have to expose the admin interface to the entire internet. Default passwords, predictable panel addresses and unused “test” accounts are the easiest things to forget in the rush. In the OWASP Top 10:2025, this sits under both authentication failures and security misconfiguration.

2. Customer login and attempt limits

A customer account holds order history and saved addresses; that is personal data. Limit login attempts against the account itself, or apply a temporary lockout. OWASP recommends tying the failure counter to the account, not the source IP; otherwise attempts can continue from many addresses. On login, password-reset and registration forms, return a generic message instead of “this email is not registered”.

Require multi-factor authentication at least for administrators and high-privilege actions. Forcing it on every shopper may not be practical in every store; do not postpone it for the admin panel.

3. The password-reset flow

A reset link should be single-use and short-lived, delivered by email, and invalid once it has been used. Do not put the old password or a long-lived session key in the link. After a successful reset, existing sessions should be ended and the user informed.

Secret questions, easily guessed codes, or “type the new password on this form immediately” weaken the flow. The OWASP Authentication Cheat Sheet treats account recovery as a risk area in its own right.

4. Session cookies and a real logout

The OWASP Session Management Cheat Sheet notes that, for a time, a session identifier is as strong as the authentication that created it. Cookies should carry Secure, HttpOnly and an appropriate SameSite value. The session ID should be long and unpredictable, and it should be renewed after a successful login; otherwise session fixation becomes possible.

A “log out” button must invalidate the server-side session, not only delete the browser cookie. Storing the session token in localStorage exposes it if a cross-site script runs; the cheat sheet advises against this.

5. Payment and checkout

Login and checkout pages should be served only over HTTPS, with no mixed (HTTP) content. Security headers and current TLS are the first layer visible from outside. Keeping card data on your own server is an unnecessary risk for most small stores; payment should go through an authorised provider, by redirect or an embedded component. This article is not a PCI certification or a QSA assessment.

Do not accept payment-provider notifications (webhooks) without a signature or shared secret. Do not trust a “payment successful” message shown in the browser, or a price field the client can change. In unusual paths — campaign coupons, partial payment, timeouts — check that the order’s “paid”, “cancelled” or “shipped” state stays consistent.

6. Third-party scripts on the payment page

A chat widget, ad tag, heat-map tool or coupon helper added to checkout can reach data in that page at browser level. Before the campaign, inventory these scripts: which ones are still needed, who injects them, and how their integrity is checked? Turn unused tags off.

Using a ready-made commerce platform (ikas, IdeaSoft, Ticimax, Shopify, WooCommerce) does not remove this check; plugin and theme updates belong on the same list. This is not a plugin scan for one platform. The point is to know whose code runs on the payment page.

7. Orders, addresses and logs

OWASP Top 10:2025 ranks broken access control first. Opening another customer’s order, invoice or address by changing a number is a scenario worth testing in the member area. For every record, “does this object really belong to this session?” should be asked both in the site and in the API.

Admin logins, failed sign-ins, password resets, payment errors and permission changes should be logged, and alerts should actually reach someone. The Board’s Decision 2019/10 expects notification to the Authority within 72 hours of learning of a personal-data breach. Without adequate logs, you learn of a breach late. Article 12 of Law No. 6698 also requires the data controller to take appropriate technical and administrative measures. This list is not legal advice or a certificate of compliance.

How to use these checks

Not all seven have to be closed in a single night. Before campaign week, admin access, login and reset, session cookies and payment notifications usually come first. Whether member orders can be read without authorisation, and the script list on the checkout page, belong in the same group.

Domain email authentication (SPF, DKIM, DMARC) is left out of this list; fake copies of discount announcements are a separate subject, covered in the email authentication article. For TLS and headers visible from outside, the free mini external check is a passive look; it is not a penetration test and involves no unauthorised probing.

Before Efsane Kasım (Turkey’s November sales period), written-scope security packages are also available for approvals given by 18:00 on Friday, 20 November 2026 (Turkey time, UTC+3). You can start with the mini check and write to us if you wish. No test starts without written authorisation from the system owner. This article is not a guarantee of security or of legal compliance.

Sources