TAP TAP GO
Understand the decision
Create a clearly labelled set of official access routes for the services that matter to your work. Include account administration, support and documentation where they are separate. Verify each route directly before distributing it to the team. The purpose is not to certify every future page or message as safe; it is to give colleagues a familiar starting point when they need to check a claim independently.
A practical workflow
Keep the list short enough to maintain. Record the owner who will update it when a provider changes domains or support procedures. Do not include passwords, recovery codes or customer-specific documents in a general team reference. During onboarding, demonstrate how to use the list when a message announces a supposed account problem. Review the routes periodically and after provider changes. A neglected list can create the same confusion it was meant to prevent, especially when an old support page no longer represents the service.
Hypothetical example
A small business keeps verified links for its publishing, document and email services in an internal guide. When an unexpected message requests a login, staff open the service from the guide and check the account directly. The guide contains no credentials and has a named maintainer.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Further reading: CISA: Secure Our World ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
