Arcor's Three-Month Security Transformation with ALLOut

Arcor’s Three-Month Security Transformation with ALLOut

Arcor, a major Latin American industrial group, successfully overhauled their JD Edwards EnterpriseOne 9.0 security system in three months using the ALLOut Security tool set. This project involved restructuring menus, creating “super-roles,” and automating security settings to meet regulatory requirements and manage 5,000 user profiles across seven countries.

Client in Focus

Arcor is a leading industrial group based in Argentina, specializing in the production of candy, cookies, chocolates, ice creams, and various food products. Operating across seven countries in Latin America, Arcor serves a diverse market with a workforce of 5,000 active users. Known for its extensive product range and significant market presence, Arcor continues to expand its reach and innovate within the food industry.

Client in Focus

Discover our industry leading expertise

Industry Insights

Reporting on User Access in JD Edwards
July 1, 2021
Auditing changes within E1 can seem daunting! But you can easily audit your History Table for User, Role or Menu changes and identify what was done, when, by whom. Your auditors and going to love this!

When Company or Business Unit Row Security Isn’t Enough
July 12, 2018
We talk about how row security works, how to best take advantage of it and how to avoid the pitfalls as we walk through the struggles experienced by a recent international customer.
Watch On-Demand

Upcoming live events

From Guesswork to Governance: Prinova’s Security Journey
February 14, 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.

Arcor’s Three-Month Security Transformation with ALLOut

Arcor’s Three-Month Security Transformation with ALLOut

Client in Focus

Challenge

Solution

Results

Products Used

CombiRoles

MenuPlus

ProfilePlus

Risk Management

Risk Reporting

SecurityPlus

SoDMaster

Download the full case study and discover Arcor's Three-Month Security Transformation with ALLOut

Client in Focus

Discover our industry leading expertise

Industry Insights

Reporting on User Access in JD Edwards

On-demand webinars

When Company or Business Unit Row Security Isn’t Enough

Upcoming live events

From Guesswork to Governance: Prinova’s Security Journey

Empower your security team