SanCor's Efficient JD Edwards Security Upgrade with ALLOut

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.

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.

Client in Focus

Discover our industry leading expertise

Industry Insights

4 Steps to Prepare for your SOX audit
July 1, 2021
Identify your internal business processes
Identify rules (or buy the ALLOut rule set)
Identify conflicts (run ALLOut’s SOD reports)
Remediate (fix) or Mitigate (excuse)

Feature Spotlight: 5 Roadmaps to Successful Projects with ALLOut Security
December 19, 2024
A healthy risk management and compliance strategy requires a best-fit approach to security and accountability in JD Edwards. The question is, how do you get there? During this session, you will be introduced to 5 strategic roadmaps for common security scenarios that you may recognize as your own. No matter where you are on your journey, we’ll be featuring mission-critical solutions that work for you
Watch On-Demand

Upcoming live events

BLUEPRINT 4D – Las Vegas!
9 Jun 2025, 12:00 am
Join the ALLOut Security team at the Venetian in Las Vegas, for what’s set to be yet another engaging conference!
View Event
SoD Risk in JDE: See it. Control it. Prove it.
July 16, 2025
Our next-generation SoD solutions are designed to meet the needs of modern GRC initiatives, tailored to IT, Finance, Audit, and Security teams alike. Align SoD oversight with your evolving control environment through consolidated processes that scale across hybrid environments, cloud platforms, M&A activity, and cross-application integrations
Register Now
Implementing Access Change Control in JD Edwards
May 21, 2025
In this joint webinar hosted by ERP Suites and supported by ALLOut Security, you’ll learn how to implement a secure, repeatable process that protects production environments without slowing down your team.
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.

SanCor’s Efficient JD Edwards Security Upgrade with ALLOut

SanCor’s Efficient JD Edwards Security Upgrade with ALLOut

Client in Focus

Challenge

Solution

Results

Products Used

CombiRoles

ProfilePlus

SecurityPlus

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

Client in Focus

Discover our industry leading expertise

Industry Insights

4 Steps to Prepare for your SOX audit

On-demand webinars

Feature Spotlight: 5 Roadmaps to Successful Projects with ALLOut Security

Upcoming live events

BLUEPRINT 4D – Las Vegas!

SoD Risk in JDE: See it. Control it. Prove it.

Implementing Access Change Control in JD Edwards

Empower your security team