Sign-in and access
Cover single sign-on (SSO), roles, the access each person needs, sign-in limits, and who can run the website.
Review our architecture for ERP access, SSO/MFA, tokenized payments, and hosting.
Use this as the approach for the first security conversation.
Cover single sign-on (SSO), roles, the access each person needs, sign-in limits, and who can run the website.
Which customer, price, order, and bill information moves between the ERP and the website?
How payment data is handled, which provider is involved, and what the ERP sees.
How do we launch and keep records, watch the website, and back up information? How do we handle problems and review changes?
Request the current security summary and setup plan, plus the supplier list and review papers.
Who leads access reviews? Who handles support access and customer data requests?
Security is a focused review, not a badge. Request the current paperwork and confirm the claims that matter to your business.
Bring your information types, connection plan, and supplier review. We will map how information moves and the checks around it.
If a requirement is not met, say so early. A clean no is better than a vague yes.
Read the security summaryThese are the questions that change the plan.
Start with the ERP and the website. Add the payment provider, and any analytics or support tools.
Prices, order history, and account information may need different handling. Treat each with the right level of control.
Name the roles, who approves access, and how often it is reviewed.
The answer should name who leads, how you communicate, and what proof you keep.
Security is part of setup, not a separate file.
Tell us what your security team needs to see, and we will keep the conversation honest.