Over the past six months, I built a custom web-based system for a growing retail business. Our workflow involves buying products from customers, reverse logistics, required holding periods, inventory intake and transfers, price matching, product searches, eBay and Shopify integrations, automated listings, and reporting requirements tied to local databases. Standard systems such as Square and Shopify do not handle those processes well, so this application manages our operations rather than credit-card processing. Shopify handles payments separately.
The application is currently hosted on Vercel and accessed through a normal website from Windows PCs in several stores. As we expand, I want to hire an experienced security professional, but I would like to understand the basics first so I can evaluate candidates and ask useful questions.
Would packaging the website as a Windows EXE or wrapper make it safer, or is a browser-based application fine if the server-side security is designed properly? What should I do to secure the store computers, prevent unauthorized remote access, protect the database and credentials, configure authentication and permissions, monitor activity, segment the network, and maintain reliable backups? I understand that backups are for recovery and should not be treated as the security plan. I am looking for practical guidance on what to assess and what kind of security specialist to hire.
3 Answers
Do not judge security by the fact that nothing has gone wrong yet. Have someone independent review the source, deployment configuration, authentication flows, integrations, permissions, logging, and incident-response process. Make sure payment responsibilities are clearly separated from the custom system, but still document what customer and inventory data it stores and check applicable privacy, insurance, and compliance requirements. Backups should be isolated from ordinary credentials, protected from deletion or ransomware, and restored on a schedule. A good hire should be able to explain threat modeling, secure architecture, vulnerability testing, least privilege, monitoring, and breach response in plain language—not just offer a list of products.
A Windows wrapper would mostly change how the application launches; it would not secure the backend by itself. Keep the application web-based and focus on server-side controls: strong authentication with MFA, role-based access, least-privilege service accounts, strict input validation, rate limiting, audit logs, secure HTTPS configuration, and no direct database access from client devices. Keep the database private, store secrets only in the deployment secret manager, and make sure backups are encrypted and regularly tested. Ask a security consultant to perform threat modeling and an application and infrastructure assessment, including what happens if a store terminal is compromised.
Treat the store computers as dedicated terminals. Use Windows Assigned Access or kiosk mode, separate standard user accounts for daily operation, no local administrator rights, automatic patching, endpoint protection, disk encryption, host firewalls, and restricted remote-administration tools. Lock down BIOS and boot settings where practical, control removable media, and limit what users can browse or install. Put the POS devices on their own VLAN or network segment, separate from guest Wi-Fi and office systems, and allow only the traffic they actually need. Restrict access to the application by identity and, where appropriate, by managed device or store network rather than relying on an obscure URL.
A dedicated standard Windows account means the employee uses an account without permission to install software or change system settings. Administration should happen through a separate admin account, ideally managed centrally, rather than giving the cashier account full privileges.
That makes sense. I was mainly wondering whether the EXE would add a meaningful security boundary, but I’ll prioritize the server-side controls and get an experienced person to review the design.