Traditional EDI Security

Over the years, several methods have been developed
to make EDI transmissions secure.

Private Data Networks

EDI transactions are often send by way of closed private data networks (which operate on a fee-basis).

Members must log on with proper password information to send and/or receive files.

Document Integrity

EDI transmissions contain information describing how many lines are in each document, and how many documents there are per transaction.

EDI transmission are given control numbers, a unique series for each sender.

Document Integrity

EDI transmissions contain information describing how many lines are in each document, and how many documents there are per transaction.

EDI transmission are given control numbers, a unique series for each sender.

ERP Security

A very basic review. Your ERP provider will give you more information.

Physical Machines

Keep valuable ERP hardware in a secure environment, safe from physical damage and theft.

Data Backups

Configure an ERP backup plan, including at least some backup files stored off-site.

Physical Access

Limit the people who have physical access to the ERP hardware.

Remote Access

Weigh the convenience of remote access against the risk of interception of your logon information.

RunB2B Security

RunB2B employs all basic EDI security measures, plus several additional safeguards.

Alerts

Set up alert conditions, such processing of large transactions.

Receive custom alerts

Place transactions on hold

Encryption

Encrypt all transmissions between yourself and RunB2B.

Error Notification

Be informed of any errors in your data structure.

RunSecure Token

As an added security measure, use a RunSecure encryption token.

Receive dynamic, single-use passwords.

Use to confirm password changes.

Require to be present at all times, for an additional level of security

Notifications of Data Anomalies

Be warned of any unusual data patterns, such as part numbers which do not follow expected patterns, or usage of new address locations.