SleekplanSleekplan
All ideas

Record sign-ins and security events in the audit log

Description: Add team members' sign-ins and account security events to the audit log: successful sign-ins, with the method used (password, Google, single sign-on) failed sign-in attempts on a team member's account two-factor authentication turned on or off password changed or reset Each entry should show the time, the team member, the event, the method and the IP address, like the other entries in the log. A team member can belong to several workspaces, so the event should appear in each of their workspaces that has the audit log. Problem: The audit log shows what team members change, but not who signed in, when and from where. Security reviews and compliance audits (for example ISO 27001 or SOC 2) ask teams to show successful and failed access attempts. Without them it is also hard to spot a compromised account early, such as repeated failed attempts or a sign-in from an unexpected IP address. Benefit: One place to answer who had access, and when Spot suspicious sign-ins and failed attempts early Evidence for access reviews and audits without asking support

Activity · 0
No comments yet. Be the first to weigh in.

More in Feature