Get demo Log in Sign up

Getting Started

Endpoints

Patch Management

Vulnerability Management

Software Deployment & IT Assets

Automation & Remote Desktop

Real-Time Reports & Alerts

Account Access & Management

SSO Authentication

Security Concerns

Integrations

Need Help?

Action1 5 Documentation 5 Getting Started with Endpoint Takeover Prevention

Getting Started with Endpoint Takeover Prevention

This guide is intended for first-time users of Action1 and can be used for evaluation purposes. It explains how to:

  • Connect your target Windows, Linux, or macOS endpoint to Action1.
  • Configure Endpoint Takeover Prevention (ETP) to protect your security-sensitive operations.
  • Identify and deploy the updates your target endpoint is missing.

By the end of the main walkthrough, you will have the following set up:

  1. Action1 key and its protecting passphrase created and securely stored. A backup Enterprise Admin account with an active Action1 key will also be configured.
  2. Your target endpoint shown as Connected and protected with ETP in the Action1 console.
  3. A list of the endpoint’s missing OS and application updates that you can automatically deploy in minutes.

NOTE: This guide only covers the initial configuration and usage scenarios implemented using the Action1 web console. To learn how to use the variety of Action1 features, configuration options, and API capabilities, refer to the Action1 REST API documentation.

Before You Begin

You will need the following to start the evaluation walkthrough:

  1. An Action1 account with the Enterprise Admin role. Make sure it has the required permissions assigned, including the new Manage Signatures and Manage Keychain Store permissions.
  2. A Windows, macOS, or Linux test endpoint and permissions to install software on it.

NOTE: Use a test endpoint whose update installation and possible reboot will not interrupt production work.

  1. Administrative access to that endpoint.
  2. A secure location for your passphrase (and, if you plan to use local key storage, a separate secure location for your Action1 key file).
  3. Also, another user with the Enterprise Admin role in Action1 will be required – this person will become a backup administrator, with their own active Action1 key.

To learn more, see Explore Endpoint Takeover Prevention.