Is multi-factor sign-in required for all company email accounts?
Yes · Partly · No · Not sure
What they’ll ask for
The sign-in policy for company email accounts, with its exceptions.
SECURITY SNAPSHOT
Answer 26 questions about your security practices and get suggested next steps. About fifteen minutes. This self-check is based on your answers; it is not an audit and does not test systems or verify your answers. Your answers stay in memory on this page and are discarded when you leave.
No account or email required. Answers are not sent to Piton or saved on your device.
Check your company’s public DNS, email and web settings.
Check a domain you’re responsible for. We look only at public settings. How this check handles data.
Use this printable checklist to discuss the controls and collect evidence. Enable JavaScript for the scored self-check.
Yes · Partly · No · Not sure
The sign-in policy for company email accounts, with its exceptions.
Yes · Partly · No · Not sure
The sign-in policy for cloud consoles, with its exceptions.
Yes · Partly · No · Not sure
The sign-in policy for administrator accounts, with its exceptions.
Yes · Partly · No · Not sure
The offboarding checklist and two recent leavers with timestamps.
Yes · Partly · No · Not sure
A restore test record with the date, system and time taken.
Yes · Partly · No · Not sure
The backup isolation or immutability settings and the accounts that can change them.
Yes · Partly · No · Not sure
The update deadline and a current compliance report for company laptops.
Yes · Partly · No · Not sure
The update deadline and a current compliance report for company-managed servers.
Yes · Partly · No · Not sure
The update deadline and a current compliance report for cloud services your team maintains.
Yes · Partly · No · Not sure
The laptop inventory and device-management enrolment report.
Yes · Partly · No · Not sure
An encryption-status report covering the laptop inventory.
Yes · Partly · No · Not sure
An endpoint-protection coverage report showing active devices.
Yes · Partly · No · Not sure
The account activity log sources and their central retention settings.
Yes · Partly · No · Not sure
The alert routing settings and the assigned response owner.
Yes · Partly · No · Not sure
The current written incident response plan.
Yes · Partly · No · Not sure
The assigned incident decision-maker and their documented authority.
Yes · Partly · No · Not sure
The date and notes of the most recent incident exercise.
Yes · Partly · No · Not sure
The security owner’s name, role and assigned authority.
Yes · Partly · No · Not sure
The reporting schedule and the most recent security report to leadership.
Yes · Partly · No · Not sure
The policy set with its approval dates.
Yes · Partly · No · Not sure
A review of policy commitments against current practice, with any exceptions.
Yes · Partly · No · Not sure
The vendor inventory showing which data each vendor holds.
Yes · Partly · No · Not sure
The pre-contract review process and a completed vendor security review.
Yes · Partly · No · Not sure
The AI use policy identifying approved tools and allowed customer data.
Yes · Partly · No · Not sure
The shipped AI feature inventory, including data flows or confirmation of no AI features.
Yes · Partly · No · Not sure
Dated evidence supporting the answers, starting with the critical controls.
Discuss the checklist with contact@pitonsecurity.com.
This is a planning aid, not an audit, penetration test, certification, legal advice or guarantee.