Logo

ARCON PAM (Standard)

Reviewed by GoLicense Technical Team ·
Last updated:

ARCON PAM (Standard) is a privileged access management solution for organizations that need core controls over administrative access to critical systems. ARCON positions Standard for smaller IT environments, with password vaulting, multi-factor authentication, single sign-on, role-based access, session monitoring, and reporting.

Before purchasing, define who needs privileged access, which systems they will use, and what evidence auditors require. Match those workflows to the proposed Standard entitlement, then confirm licensing quantities and deployment requirements in the quotation.

Request ARCON PAM (Standard) Pricing: Send your privileged-user count, target-system inventory, expected simultaneous sessions, and preferred deployment. Include the current agreement for renewals or expansions.

Send your privileged-user inventory, target systems, and deployment requirements for an ARCON PAM (Standard) quotation.

Request ARCON PAM Quote

Is ARCON PAM (Standard) Right for Your Requirements?

Use the following guide to translate access-control objectives into requirements for the proposed package.

Your Requirement Capability to Evaluate What to Confirm Before Ordering
Protect administrative credentials Password vault and password management Target compatibility, password policies, and dependent services
Authenticate privileged users MFA and SSO Required identity provider, authentication method, and connector compatibility
Limit access by job responsibility Role-based access management User groups, target mappings, and administrative separation
Review privileged activity Session monitoring and recording Supported connection types, playback, storage, and retention requirements
Produce audit evidence Reporting Required reports, auditor permissions, and export needs

For a broader explanation of these controls, read our privileged access management solutions guide. Use the ARCON licensing portfolio to review the vendor’s other offerings before confirming the edition.

How to Scope ARCON PAM (Standard) Licensing

Keep users, target systems, privileged accounts, and simultaneous sessions as separate inventory fields. These figures help scope the deployment, but they should not be treated as interchangeable license units.

Request a written definition of the chargeable metric, included quantity, expansion rules, and contract duration. Confirm whether the offer is subscription-based or includes any perpetual rights, and distinguish software entitlement from maintenance and support.

Do not interpret statements about onboarding scale as an unlimited commercial entitlement. The order should explicitly identify permitted capacity and any architecture or edition limits.

Ordering Guide and Deployment Example

The bill of materials should identify Standard edition, the verified licensing metric and quantity, deployment components, support period, and implementation services. Include HA, disaster recovery, or additional environments only after their availability and licensing have been confirmed. Use the exact supplier-verified part numbers in the offer.

Example: Controlling Access for a Small IT Team

Suppose 12 administrators manage 30 Windows and Linux systems and several database services. The organization requires MFA, role-based access, and session recordings retained for 90 days.

These are hypothetical planning inputs, not Standard edition limits or a calculated license quantity.

Prepare These Details Before Ordering

Provide target operating systems and versions, databases, access protocols, privileged accounts, authentication integrations, recording requirements, and site layout. Identify service-account dependencies before planning password changes.

ARCON PAM (Standard) Pricing & Quote

Request pricing against the confirmed access scope and deployment design. A current public Standard price list and definitive charge metric were not verified during the November 2026 review, so the quotation should establish both before purchase.

Compare offers using the same edition, capacity definition, contract dates, and support coverage. Ask whether implementation, connector configuration, training, storage, infrastructure software, and recovery environments are included.

For renewals, provide the existing entitlement and support expiry date. For expansions, describe what is changing rather than purchasing an assumed number of extra users or devices.

ARCON PAM Standard price quote banner

Need ARCON PAM Pricing?

Share your access scope, target systems, and deployment needs for a tailored Standard edition quote.

Get Price Quote →

Buying, Delivery and Activation with GoLicense

1. Confirm the Licensing Scope

Submit the inventory and required workflows. Before approving the order, confirm the supplied edition, licensing metric, quantities, price, delivery timeframe, and implementation responsibilities.

2. Confirm the Deployment and Ownership Details

Identify the organization that will own the entitlement and the administrator responsible for deployment. Confirm whether the order concerns a new installation, renewal, or expansion.

3. Receive and Verify the Entitlement

Check the delivery against the approved quotation, including edition, capacity, validity, and support. Agree on the actual delivery method and any installation identifiers required before processing the order.

4. Complete Activation and Validate Access

Follow the activation instructions supplied for the purchased version. Confirm that the entitlement is accepted before onboarding a pilot group. Then test authentication, authorized target access, credential handling, session recording, and auditor access against the acceptance plan.

Document who performs installation and configuration, which tasks GoLicense assists with, and which require the customer or an implementation specialist. A license delivery alone does not complete a PAM rollout.

Restricted Networks and Deployment Prerequisites

If the environment has no direct internet access, request written confirmation of the supported activation, renewal, and update workflow for the supplied version. Also check connectivity requirements for MFA, identity services, and other integrations. Cloud deployment should not be assumed to mean a vendor-operated SaaS service.

Before You Order: Prerequisites and Common Mistakes

Pre-Order Checklist

Common Buying and Deployment Issues

Assuming Standard includes every ARCON capability: Obtain the current edition-specific feature schedule before purchase.

Changing passwords without checking dependencies: Identify services, scripts, and scheduled tasks that use each account, then test changes in a controlled pilot.

Underestimating recording storage: Plan retention, access controls, and backup requirements before onboarding production sessions.

Confusing authentication with authorization: Successful MFA should still lead only to the targets assigned to that user.

Skipping recovery testing: Agree on emergency access and restoration procedures before making PAM the normal administrative access route.

Ready to order? Send your requirements and request an ARCON PAM (Standard) quote.

Request ARCON PAM Quote →

Related Privileged Access Management Resources

Frequently Asked Questions