Pernod Ricard's Global Security Rollout with ALLOut

Pernod Ricard’s Global Security Rollout with ALLOut

Pernod Ricard implemented ALLOut Security tools to manage and remediate their JD Edwards EnterpriseOne security across 30 countries. The company needed to comply with various corporate governance legislation and enhance their segregation of duties reporting, which was achieved through ALLOut’s SecurityPlus. The successful transition to a “Deny All” security model improved their security framework and compliance capabilities.

Client in Focus

Pernod Ricard, headquartered in Paris, is a global leader in the wine and spirits industry. The company boasts a unique portfolio of premium and international brands, including ABSOLUT, Chivas Regal, Jameson, and Martell. With over 18,000 employees and annual revenue of €7 billion, Pernod Ricard operates a decentralized organization structure, encompassing six brand companies and 70 market companies worldwide.

Client in Focus

Discover our industry leading expertise

Industry Insights

Segregation of Duties Concepts Explained
July 1, 2021
The concept of internal controls which attempt to ensure that no single individual has the authority to execute two or more conflicting, sensitive transactions with the potential to impact financials.

Best Practices with E1 Menus and Pages With StartOut
October 30, 2017
Learn how the ALLOut toolset can automate your menu, role and security set-up process in a fraction of the time than it takes using the standard interfaces.
Watch On-Demand

Upcoming live events

From Guesswork to Governance: Prinova’s Security Journey
February 24, 2026
A sustainable security and compliance model depends on visibility and confidence. For Prinova, that meant moving from reactive security management to taking control directly within JD Edwards.
Register Now

Empower your security team

Save time, enhance risk visibility and be audit-ready with ALLOut Security for JD Edwards.

Request a Demo

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

Pernod Ricard’s Global Security Rollout with ALLOut

Pernod Ricard’s Global Security Rollout with ALLOut

Client in Focus

Challenge

Solution

Results

Products Used

CombiRoles

MenuPlus

ProfilePlus

Risk Management

Risk Reporting

SecurityPlus

StartOut

Download the full case study and discover Pernod Ricard's global security rollout with ALLOut

Client in Focus

Discover our industry leading expertise

Industry Insights

Segregation of Duties Concepts Explained

On-demand webinars

Best Practices with E1 Menus and Pages With StartOut

Upcoming live events

From Guesswork to Governance: Prinova’s Security Journey

Empower your security team