8.1.5: Third Party Accounts


Enable third-party vendor accounts only when needed and monitor when in use



  

Fully functional free edition for up to 10 endpoints with no expiration date. More details >







Trusted by Thousands of Customers Worldwide:
Action1 Customers
Organizations shall never allow 24/7 access to their systems by third party vendors for support and maintenance purposes, because this increases the chances of attack. You should only enable vendor accounts when needed and disable as soon as they are done working to prevent any misuse. When vendor accounts are used, their activity must be monitored.

This Action1 query can help to assess your endpoints for vendor account usage. You have to provide a list of vendor account names in order to check their usage and then verify the usage timeframes.

Latest Release: Action1 Endpoint Security Platform 2.2, May 4, 2020.
For more information, please refer to Action1 Online Documentation

  

Fully functional free edition for up to 10 endpoints with no expiration date. More details >





Achieve More With Our Integrations and RESTful API


Action1 provides RESTful API and integrates with the following systems so you can get most out of your deployment:

Action1 Integrations




Hundreds of Organizations Worldwide Use Action1 Platform



Midwestern Energy Company

Being a part of the national energy grid infrastructure puts a lot of cybersecurity responsibilities on our company. Action1 helps to implement it.

Midwestern Energy Company

European Construction Conglomerate

Action1 plays a critical role in our cybersecurity strategy. The ability to instantly understand what is happening on your endpoints is priceless.

European Construction Conglomerate

City Government in Georgia

Our city prides on being one of the most digitally transformed cities in the region. Without Action1, the risks of managing the infrastructure were too high.

City Government in Georgia




Related Product Features:

8.1.1: Assign Unique User IDs
    All users must be assigned a unique ID before granting them access to cardholder data
8.1.2: Management of User IDs
    Control addition, deletion, and modification of user ID, credentials and other identifier objects
8.1.3: Revoke Access for Terminated Employees
    Ensure that any terminated users lose their access to corporate systems
8.1.4: Inactive User Accounts
    Remove or disable user accounts that have been inactive for over 90 days
8.1.6: Account Lockouts
    Limit multiple invalid login attempts by locking out the user ID after 6 attempts
8.1.7: Account Lockout Duration
    The lockout duration must be at least 30 minutes or until re-enabled by administrator
8.1.8: Idle Sessions
    Require user re-authentication after a session has been idle for more than 15 minutes
By continuing to use our website, you agree with our use of cookies in accordance with our Privacy Policy. You can reject cookies by changing your browser settings.     
Ok, got it