PHP SDK for user monitoring¶ Sqreen protects your application users against major threats, such as account takeover, password bruteforce, suspicious activities coming from TOR or an unusual VPN. Advanced User Context allows you to set up user monitoring in your application with flexibility and powerful extra features. You will need to integrate Sqreen SDK in your application. User monitoring SDK¶ The Sqreen SDK integration relies on three methods: signup_track, auth_track and identify. Here is a full implementation example: <?php // in the signup method, when the user account is created for the first time: $user = signup($email, $password); sqreen\signup_track(['email' => $email]) // ... // in the signin method, when a user creates a new session: $user = login($email, $password); sqreen\auth_track($user !== NULL, ['email' => $email]) // ... // On every request to map the authenticated user to the request $user = login($email, $password); sqreen\identify(['email' => $email]) ?> Login tracking¶ sqreen\auth_track is the SDK method to call on user login activity. <?php sqreen\auth_track(is_login_successful, ['email' => $email]) ?> The auth_track function accepts two positional arguments: <?php sqreen\auth_track(success, user_identifiers) ?> The first argument is a boolean indicating if the login attempt was successful or not (true or false). The second argument is an array with your user identification information. Sqreen's interface uses it to help you identify which users are at risk, or which are attacking your application. The hash keys and values must be strings. Sqreen integration at signup and login You should not call Sqreen.auth_track each time you check a user session in your application. Signup tracking¶ sqreen\signup_track is the SDK method to call when creating a new user account at signup. <?php sqreen\signup_track(['email' => $email]) ?> The signup_track function accepts a single argument: <?php sqreen\signup_track(user_identifiers) ?> user_identifiers is an array representing your identification information. Sqreen's interface uses it to help you identify which users are at risk, or which are attacking your application. The hash keys and values must be strings. Session tracking¶ sqreen\identify is the SDK method to map a user to the current HTTP request. Block users with security automation You must implement the identify method to block users with Security Automation When the request is not identified using this method, Sqreen falls back to login tracking information to map a user. It's a best effort approach based on the recent activity of users on the request's IPs. The identify function accepts two positional arguments: <?php sqreen\identify(user_identifiers, traits) ?> The first argument is an associative array representing the identification information. Sqreen's interface uses it to help you identify which users are at risk, or which are attacking your application. The hash keys and values must be strings. The second argument is an optional associative array of traits about the user. The hash keys and values must be strings. User traits At the moment, we do not display or process the traits. In a future release, we'll display them to help attack investigation and allow you to build custom workflows. Interested in this feature? Contact us. Block users (security automation)¶ When using the Security Automation built-in "block user" security response, you should implement identify and auth_track methods to block users at login or during their session. Otherwise, Sqreen is not able to map a user context to requests performed on your application. Learn more about login and session tracking. User identification¶ For users with a single identification value, such as an email address or nickname: <?php sqreen\auth_track(true, ['email' => $email]) ?> User monitoring and PII Avoid sending sensitive data and PII (personally identifying information) to us. Visit this blogpost to learn some best practices around user tracking. For users with a composite primary key (more than one value), send all the values to identify the user accurately in Sqreen's user interface. For example, if you are are operating a whitelabel platform and it identifies your users by their email and the shop ID, you can send these identifiers like this: <?php sqreen\auth_track(true, ['email' => $email, 'platform_id' => $platform_id]) ?> This also applies to the signup_track and identify functions. Note that the three calls rely on the same identity format in order for Sqreen to map the activities to a single user. The Sqreen SDK only accepts user identifiers Do not send any other information (like the auth failure reason). Sqreen will consider them as part of the user identifier, and will not be able to merge successful and failed authentications. Primary key¶ Sqreen tries to determine a primary key amongst the keys you provided. Sqreen uses the following keywords to determine the user primary identification key: email, mail, e-mail, username, login. If Sqreen cannot find any of those keys, it uses the first key in alphabetic order. If Sqreen finds more than one key, it uses the first in the sequence mentioned above.