Skip to main content
Founder-Led · Practicing Since 1997 Founder-led. Specialist-delivered. Every engagement follows standards developed by Tony Paris over 29 years.
Security & Compliance

Two-pass verification on a SaaS

By Tony Paris · November 4, 2026 · 2 min read

Drafted with AI and published by AppWT.

I added a second check to protect critical actions in a SaaS. I share constraints, my approach, and practical steps you can copy this week.

The industry and problem

I added a two-pass verification to a SaaS used by a healthcare operations group to manage sensitive account settings. A single confirmation click could delete records or change payout details. I needed a second check that reduced risk and kept daily work moving.

Constraints

  • Keep it fast for busy staff on phones and tablets.
  • Add no extra app or device. Use channels they already had.
  • Support both single sign on and passwords.
  • Meet accessibility basics with clear focus order, labels and error messages.
  • Provide an audit trail for reviews and incident response.

Two pass means a user confirms a risky action with a separate step, such as a typed phrase or a code. If you handle HIPAA regulated data, confirm specific requirements with your attorney or compliance advisor.

My approach

I mapped critical actions first. That list included destructive deletes, permission changes, payment destination edits and large data exports. Then I matched each action to a two pass pattern that fit the risk.

  • Typed confirmation gate. Show a plain summary of the change and require the user to type a short confirm phrase.
  • Reauthentication. If the session was old, ask the user to sign in again before proceeding. Single sign on means using one login to access several systems.
  • One time code. Send a code to a verified channel such as email or an authenticator app and require that code to continue.
  • Two person approval. For the most sensitive changes, require a second authorized person to approve.
  • Timed hold. Queue the action for a short window so the requester can cancel if it was a mistake.

I logged who requested and who approved, with timestamps and change details. I set rate limiting, which slows repeated attempts from the same source, and I added firewall rules to reduce automated attacks. I wrote a short procedure so staff knew when to approve and when to escalate.

What I learned

The second check must match the risk, use plain language and be predictable. Small, well placed friction helps people slow down and confirm intent without blocking real work. Test the flow on mobile and with a screen reader, review roles often, and keep a documented emergency bypass for authorized leaders.

How I can help

I design and implement second checks and access controls as part of Security & Compliance > Features & Add-ons, and I can pair them with WAF & Firewall or HIPAA Compliance as needed.

Get the next one in your inbox

Pick your topics and how often, from weekly to quarterly. I send a confirmation email first, and you can change or stop it any time.

Get more like this by email

CDN and WAF tuning for safety

I show how I tuned a CDN and WAF on a live SaaS platform to boost safety without hurting user experience, with steps you can copy this week.

Firewall change management

I share a practical firewall change management checklist with approvals, testing, and rollback steps you can use this week.

All Security & Compliance articles

Share This Page
Awards & Recognition
AI-generated AppWT theme song art: two singers in black and gold on a rooftop above the Detroit skyline at sunset

Accessibility

by AppWT Web & AI Solutions
🛡️ Accessibility Profiles
📝 Content Adjustments
100%
100%
1.4
0px
🎨 Color Adjustments
100%
🎛️ Orientation & Controls
♿

Accessibility Statement

Our commitment to digital accessibility and inclusive design

Our Commitment to Accessibility

AppWT Web & AI Solutions is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to achieve these goals.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

AppWT Web & AI Solutions is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Accessibility Features

  • Built-in accessibility toolbar with multiple customization options
  • Keyboard navigation support throughout the website
  • Screen reader compatibility and proper ARIA labels
  • High contrast mode and color customization options
  • Text size adjustment and font modification capabilities
  • Reading guide and focus indicators for improved navigation
  • Alternative text for all images and media
  • Semantic HTML structure for better screen reader interpretation

Technical Specifications

Accessibility of AppWT Web & AI Solutions relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Feedback

We welcome your feedback on the accessibility of AppWT Web & AI Solutions. Please let us know if you encounter accessibility barriers:

Phone: (888) 565-0171

Email: sales@appwt.com

Address: 33300 Five Mile Rd, Livonia, MI 48154 (by Appointment Only)

Assessment Approach

AppWT Web & AI Solutions assessed the accessibility of our website by the following approaches:

  • Self-evaluation
  • External evaluation
  • Automated testing tools
  • Manual testing with assistive technologies

Date

This statement was created on January 15, 2025 using the W3C Accessibility Statement Generator Tool.

Last updated: