Breach-triggered reassessment is the right idea. An annual questionnaire shows how a vendor looked on one day, and attackers don't wait for the renewal date.
A question from my corner of security (I work on payment page protection): do you treat the scripts loaded on a customer's checkout as third parties? Analytics tags, chat widgets and tag managers are vendors too, but they never get a questionnaire, and many Magecart cases started with one of them being compromised. PCI DSS 6.4.3 now asks merchants to inventory and justify each of those scripts.
Also curious how you calibrate the "≈ $1.2M exposure" figure. Showing the comparable incidents behind that number would make it much easier to take to a board.
Congrats on the launch!
Welcome to StartupBase
Join a community of founders sharing their products and discovering what others
are building.
Email sign-in is for existing accounts. New here? Use Google, LinkedIn, or X above
— your account is created automatically.
Continue with email
Enter the email address on your existing account and we'll send you a one-time
sign-in code. This does not create an account — to sign up, go back and
continue with Google, LinkedIn, or X.
Enter the verification code we sent to your email address.
Breach-triggered reassessment is the right idea. An annual questionnaire shows how a vendor looked on one day, and attackers don't wait for the renewal date.
A question from my corner of security (I work on payment page protection): do you treat the scripts loaded on a customer's checkout as third parties? Analytics tags, chat widgets and tag managers are vendors too, but they never get a questionnaire, and many Magecart cases started with one of them being compromised. PCI DSS 6.4.3 now asks merchants to inventory and justify each of those scripts.
Also curious how you calibrate the "≈ $1.2M exposure" figure. Showing the comparable incidents behind that number would make it much easier to take to a board.
Congrats on the launch!