We're dedicated to security and compliance, making protecting your business our only mission.

Since the company started-up in 2004, our team has grown significantly. Our expertise goes back to the 1980s with our founding partners, making ALLOut the most experienced team in the industry.

Discover ALLOut Security

Meet our team of experts

Linda Nelson

VP Business Success (Global)

Stefanos Stylianou

Partnerships & Alliances Director

Stefanos Loizou

Director of International Sales

Monica Otero

Director, Technology Risk & Data Assurance

Merry Petersen

Commercial Contracts Manager

Nick Birmpilis

Digital Marketing Assistant

Frosoulla Kofterou

Communications Lead

Stephanie Rey

Licensing Manager

Alex Rippingale

Technical Author

Tanya Johnson

Senior Training Consultant

Athena Monoyiou

Financial Controller

Kathy McCabe

Office Manager

Luke Phillips

JDE Security & Risk Management Architect

Adrian Prince

Senior JDE Developer

Dave Wilkins

Senior JDE & i Series Developer

Toni Pallas

Senior JDE Developer

Edward Phillips

Cloud Solutions Developer

Do you want to join our team?

If you’re interested in working with a dynamic team of professionals in a fast-paced, hands-on environment, we'd love to hear from you. We're always on the look out for talented people that share our enthusiasm of working in tech!

Discover our industry leading expertise

Industry Insights

Compliance Does Not Stop at Segregation of Duties
July 1, 2021
Really achieving compliance in system security includes managing access to confidential or critical information, ensuring only appropriate access is in place for all users, that changes are authorized.

What to do when just knowing you have a SOD Issue Isn’t Enough
August 3, 2018
Sometimes just knowing that you have an issue isn’t enough. Let us show you the tools available to manage the risk that segregation of duties conflicts imply.
Watch On-Demand

Upcoming live events

5 Roadmaps to Successful Projects with ALLOut Security [APAC]
December 18, 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?
Register Now
5 Roadmaps to Successful Projects with ALLOut Security [EMEA & AMERICAS]
December 18, 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?
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.