Nufarm Enhances Security and Compliance with ALLOut

In response to escalating complexity and inefficiency caused by over 300 user roles in their JD Edwards system, Nufarm Ltd implemented ALLOut to streamline and standardize their security processes. This solution enabled Nufarm to enforce segregation of duties controls, improve visibility into user access, and significantly reduce maintenance hours. As a result, Nufarm achieved enhanced security, operational efficiency, and successfully passed audits with improved compliance.

Client in Focus

Nufarm Ltd, headquartered in Victoria, Australia, is a leading global agrochemical company. With over 450 employees and annual revenues reaching $2.68 billion, Nufarm operates manufacturing facilities in 14 countries and sales offices in over 100 nations, ranking among the top 10 companies in its industry worldwide.

Client in Focus

Discover our industry leading expertise

Industry Insights

Mitigating Controls – Should you use them?
July 1, 2021
Mitigating controls are never as desirable as an effective segregation of duties, but in some situations, a breach of a security rule may just have to exist.

Working with Security Roles in JD Edwards
February 4, 2020
The ability to use security roles as a building block of your security efforts is an incredibly useful tool. How do you make the most of it in your implementation or daily processes?
Watch On-Demand

Upcoming live events

Escape Legacy JDE Security Tools: A Faster, Cheaper, Native Upgrade Path
January 13, 2026
Many customers of other JD Edwards Security solutions still struggle with heavy SoD, compliance, and security workloads driven by poor visibility, inefficient processes, rising costs and limited resources.
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.

Nufarm Enhances Security and Compliance with ALLOut

Nufarm Enhances Security and Compliance with ALLOut

Client in Focus

Challenge

Solution

Results

Products Used

CombiRoles

MenuPlus

ProfilePlus

Risk Management

Risk Reporting

SecurityPlus

Download the full case study and learn how Nufarm enhanced security and compliance with ALLOut

Client in Focus

Discover our industry leading expertise

Industry Insights

Mitigating Controls – Should you use them?

On-demand webinars

Working with Security Roles in JD Edwards

Upcoming live events

Escape Legacy JDE Security Tools: A Faster, Cheaper, Native Upgrade Path

Empower your security team