SanCor’s Efficient JD Edwards Security Upgrade with ALLOut

SanCor, an Argentine dairy cooperative, successfully upgraded to JD Edwards EnterpriseOne 9.1 by implementing ALLOut Security tools despite facing time constraints and a heavy workload. Partnering with ITCROSS, they used the StartOut spreadsheet to design and validate a new closed security model, integrating custom applications and streamlining menu management. This efficient implementation allowed them to complete the project on time and within budget, with plans for further security enhancements to comply with SOX law.

Download Case Study

Client in Focus

SanCor is an Argentine cooperative based in Sunchales, Santa Fe, formed by 1,400 dairy farmers. The company produces a wide range of milk-based products for both the Argentine market and international markets. With 4,700 employees, SanCor is a significant player in the dairy industry, known for its commitment to quality and innovation.

Challenge

SanCor faced a significant challenge while upgrading to JD Edwards EnterpriseOne 9.1 due to a tight timeline and heavy workload on their internal IT security team. They needed to design and implement a new security model quickly to integrate testing into the upgrade process effectively. Without a rapid setup, they risked missing the opportunity to ensure the new security design’s robustness during the upgrade.

Solution

Partnering with ITCROSS, ALLOut’s local representative, SanCor used the StartOut spreadsheet from AOS to compare standard roles against their business roles, adding custom and localization applications as needed. This method allowed them to implement a closed security model, leveraging AOS’s features to handle potential issues and streamline the security design process.

Results

The implementation of ALLOut Security tools enabled SanCor to complete their security project on time and within budget, as highlighted by their Chief Information Security Manager. The successful transition to a closed security model and the redesign of their menus using AOS tools improved their overall security framework..

Products Used

CombiRoles

ProfilePlus

SecurityPlus

Download the full case study and discover SanCor's efficient JD Edwards security upgrade with ALLOut

Download Case Study

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.