官术网_书友最值得收藏!

Monitoring the login history

Another metric that is useful for security purposes is the monitoring of every login attempt on your organization. With this metric, you know exactly who is logging in, how many times they have logged in, and from where they are logging in—for example, you can check whether your users are logging in from certain locations or using an out-of-policies browser.

Click on Setup | Identity | Login History to bring up the following page:

Login History page

This page shows up to 20,000 login attempts over the last six months. If you need more, you can download a CSV or a zipped file.

 

We can even create a filtered list to show only a subset of the records (for example, only incorrect password login attempts).

Some of the relevant information on this page is as follows:

  • Username
  • Login Time
  • Source IP: This is the IP from which the user has tried to log in. Use this information to find out whether you have a user accessing the organization outside the allowed and authorized locations (for example, check whether they are using the security token from an outside app).
  • Location: This is the inferred location based on IP address information.
  • Login Type: The kind of login used (for example, Application, Remote Access 2.0, OAuth, SAML)—that is, which methods are my users using?
  • Status: Login status (Success or the reason for failure, such as Invalid Password or User Locked).
  • Application: The kind of application used (Browser or any other custom app).
  • Browser
  • Platform: The kind of platform (for example, the operating system) used for login.
  • Login URL: Which login endpoint has been used. You can monitor whether users are using the standard login page or the My domain URL.
  • Community: The originating community.
  • HTTP Method: Using the GET method should be avoided because it may inadvertently expose the user's username and password.

By creating a new list view, we can show more columns, such as the following:

  • TLS Protocol: The encryption protocol used by a user's client application.
  • Latitude and Longitude: The accuracy depends on various factors.
  • Country, Country Code, City, Postal Code, and Subdivision: These are inferred from the geolocation:
Login History custom list view

The same information can be found on the user's record page in the Login History section.

主站蜘蛛池模板: 蓝山县| 高雄市| 罗定市| 克什克腾旗| 雷山县| 商南县| 赤城县| 兴化市| 中方县| 郯城县| 双鸭山市| 津南区| 乌鲁木齐县| 资兴市| 固始县| 莒南县| 无为县| 如东县| 伊宁县| 汨罗市| 正镶白旗| 大同市| 柞水县| 七台河市| 太保市| 兴仁县| 施甸县| 黎川县| 类乌齐县| 北海市| 绥德县| 建德市| 武宣县| 都兰县| 芜湖县| 宜宾市| 敦煌市| 沿河| 淳安县| 石城县| 资溪县|