Security Checklist for Integrating Custom and Legacy Systems

Last updated: November 2026

Integrating custom and legacy systems introduces security risks that modern API integrations rarely face: shared database credentials, unencrypted SOAP traffic, broad service accounts, file transfers containing sensitive data, and scripts with hard-coded secrets. This checklist covers 15 controls across five areas (access, credentials, data, network and operations) that security and integration teams should apply to every connection with a system that lacks a modern API. It also explains how integration platforms such as ZigiOps reduce risk by storing no transferred data and centralizing credentials.

Security reviews of integrations usually focus on popular SaaS connections: OAuth scopes, API tokens and vendor certifications. Integrations with custom and legacy systems often receive less scrutiny, even though they are frequently riskier. They tend to be built quickly, with whatever access was available, and then forgotten.

Typical findings in security assessments include database accounts with full administrative rights used by integration scripts, passwords stored in plain-text configuration files, SOAP services called over unencrypted HTTP inside the network, CSV exports of customer data left on shared drives, and integrations still running under the accounts of employees who left years ago.

None of these issues require sophisticated attacks to exploit. An attacker who gains a foothold in the network, or a curious insider, can often find integration credentials in scripts or configuration files and use them to read large volumes of data. Because the access looks like normal integration activity, it may go unnoticed. The checklist below is designed to close these gaps systematically.

Why custom and legacy integrations are higher risk

Area 1: Access control

1. Use dedicated integration accounts

Every integration should have its own account in each connected system, never a personal account and never an account shared with other applications. Dedicated accounts make activity traceable and allow access to be revoked without side effects.

2. Apply least privilege

Grant only the permissions the integration needs. For databases, restrict access to specific views or tables rather than entire schemas. For applications, use roles limited to the relevant record types and operations.

3. Prefer views and staging tables for database integrations

Create read-only views that expose only the required columns and rows. For writes, use staging tables or stored procedures that the application processes, rather than writing directly into core tables. This limits exposure and preserves business logic.

Area 2: Credentials

4. Centralize and encrypt credentials

Store credentials in a secrets vault or in the integration platform's encrypted configuration. Never store them in scripts, plain-text files or source code repositories.

5. Rotate credentials regularly

Define rotation schedules for passwords, tokens and certificates, and make rotation easy by keeping credentials in one place. Legacy systems that support only passwords make rotation especially important.

6. Use stronger authentication where available

Even older systems may support certificate-based authentication, Kerberos or integrated Windows authentication. Use the strongest method the system supports.

Area 3: Data protection

7. Minimize the data transferred

Synchronize only the fields that the target system needs. Exclude personal, financial or health data unless there is a clear purpose and legal basis.

8. Avoid storing data in the integration layer

Every copy of data is another place to secure, back up, retain and delete. Prefer integration approaches that pass data through without persisting it. ZigiOps, for example, does not store the data it transfers, keeping only minimal runtime information needed for correlation.

9. Protect files in transit and at rest

If file-based exchange is unavoidable, encrypt files, transfer them over secure protocols such as SFTP, restrict access to transfer folders and delete files automatically after processing.

Area 4: Network security

10. Encrypt all connections

Use TLS for SOAP and HTTP traffic and enable encryption for database connections, even inside the corporate network. Internal networks are not inherently trusted.

11. Restrict network paths

Allow integration traffic only between the integration platform and the specific systems and ports it needs. Use firewalls and network segmentation to limit lateral movement.

12. Prefer outbound connections to the cloud

When connecting on-premise legacy systems with cloud services, run the integration platform inside the network and make only outbound connections to the cloud. Avoid exposing legacy systems to the internet. ZigiOps can be deployed on-premise for exactly this reason.

Area 5: Operations and governance

13. Log every integration action

Record what was read and written, when, by which integration and with what result. Keep logs long enough for audits and incident investigations, and forward them to your security monitoring tools if possible.

14. Monitor and alert on anomalies

Alert on failures, unusual volumes, access outside expected hours and authentication errors. Sudden spikes in data read from a legacy database can indicate misuse.

15. Review integrations regularly

Include integrations in periodic access reviews. Confirm that each one is still needed, that its permissions are still appropriate and that its owner is still in role. Decommission unused integrations and revoke their credentials.

The 15-point security checklist for custom and legacy system integrations
AreaControlCommon gap it addresses
AccessDedicated integration accountsPersonal or shared accounts
AccessLeast privilegeAdministrator-level database access
AccessViews and staging tablesDirect access to core tables
CredentialsCentralized, encrypted storagePasswords in scripts and files
CredentialsRegular rotationCredentials unchanged for years
CredentialsStrongest available authenticationBasic authentication by default
DataMinimize transferred fieldsFull record copies
DataNo storage in integration layerShadow copies of sensitive data
DataProtect filesUnencrypted exports on shared drives
NetworkEncrypt all connectionsPlain HTTP or unencrypted database traffic
NetworkRestrict network pathsBroad internal network access
NetworkOutbound-only to cloudLegacy systems exposed to the internet
OperationsLog every actionNo audit trail
OperationsMonitor and alertSilent misuse or failure
OperationsRegular reviewOrphaned integrations and accounts

Mapping the checklist to common frameworks

The controls in this checklist align with requirements found in widely used security frameworks. Mapping them helps when integrations are reviewed during audits.

How the checklist relates to common security frameworks
Checklist areaRelated framework themes
Access controlISO 27001 access control; NIST least privilege; SOC 2 logical access
CredentialsSecret management, authentication and key management controls
Data protectionData minimization (GDPR), information classification and handling
Network securityNetwork segmentation, encryption in transit, secure configuration
Operations and governanceLogging and monitoring, supplier management, periodic access review

Exact control numbers depend on the framework version you use, so work with your compliance team to map each integration control to your internal control library.

Prioritizing remediation

Most organizations find several gaps when they apply this checklist to existing integrations. Prioritize remediation by risk:

  1. Credentials in plain text or owned by former employees. Rotate or revoke immediately.
  2. Administrator-level access. Replace with least-privilege accounts and views.
  3. Legacy systems exposed to the internet. Redesign with outbound-only connections.
  4. Unencrypted connections carrying sensitive data. Enable TLS or database encryption.
  5. Unprotected files. Encrypt, restrict and automate deletion.
  6. Missing logs and alerts. Add logging and monitoring.
  7. Orphaned integrations. Decommission and revoke access.

Integrating security into the integration lifecycle

Checklists work best when they are part of the normal process rather than an occasional audit. Add the 15 controls to the design template for new integrations, include them in the definition of done for go-live, and repeat a lighter review annually. When integrations are managed in a central platform, many controls, such as credential encryption, logging and data storage behavior, are applied by default, so reviews can focus on system-specific access.

Replacing scripts reduces risk

Many of the gaps above come from integrations built as scripts. Each script has its own credentials, logging and network access, and few are reviewed after go-live. Moving these integrations to a central platform consolidates credentials, applies consistent logging and makes reviews practical.

The obstacle is often that the platform cannot reach the custom or legacy system. ZigiOps addresses this by integrating any system through an API, SOAP, a database or a library, so even systems without an API can be moved off scripts. New connectors are typically built in about three days.

Questions to ask integration vendors

  1. Does the platform store transferred data? If so, where and for how long?
  2. How are credentials stored and encrypted?
  3. Which authentication methods are supported for databases, SOAP and libraries?
  4. Can the platform run on-premise to avoid exposing legacy systems?
  5. What logs are available, and can they be exported to a SIEM?
  6. Which independent certifications does the vendor hold? ZigiOps, for example, is ISO 27001 certified.
  7. How are custom connectors reviewed for security before delivery?

Example: securing a legacy HR database integration

An organization synchronizes employee data from a legacy HR system, backed by an Oracle database, to its cloud ITSM platform for onboarding and offboarding requests. The original integration was a script using the HR database's owner account, with the password stored in a configuration file.

  1. A read-only view now exposes only employee ID, name, department, manager, location and status.
  2. A dedicated database account has access only to that view.
  3. The integration platform runs on-premise, connects to the database over an encrypted connection and calls the cloud ITSM platform outbound over HTTPS.
  4. Credentials are stored encrypted in the platform and rotated quarterly.
  5. Every synchronization is logged, and logs are forwarded to the security monitoring system.
  6. The old script and its credentials were removed.

The integration delivers the same business result with far less exposure.

Frequently asked questions

Why are legacy system integrations a security risk?

They often use older authentication, broad permissions, unencrypted protocols, scattered credentials and limited logging, and they are reviewed less often than modern integrations.

Is direct database integration secure?

It can be, with dedicated least-privilege accounts, read-only views, staging tables for writes, encrypted connections and full logging.

Should integration platforms store data?

Storing as little as possible reduces risk. ZigiOps does not store the data it transfers.

How often should integration credentials be rotated?

Follow your organization's policy; many use 90-day rotation for passwords and shorter lifetimes for tokens where possible.

How do I connect legacy systems to cloud services securely?

Run the integration platform inside your network, use outbound-only connections to cloud services, encrypt all traffic and avoid exposing legacy systems to the internet.

What should an integration security review include?

Data flows, accounts and permissions, credential storage, encryption, network paths, data storage, logging, certifications and offboarding procedures.

Which integration gaps should be fixed first?

Start with exposed or orphaned credentials and administrator-level access, then address systems exposed to the internet, unencrypted sensitive traffic, unprotected files and missing logs.

Do internal network connections really need encryption?

Yes. Modern security practice does not treat internal networks as trusted. Encrypting database and SOAP traffic protects credentials and data from attackers who gain internal access.

How can teams keep the checklist from becoming a one-time exercise?

Add the controls to integration design templates and go-live criteria, run an annual review of every integration, and manage integrations in a central platform where many controls apply by default.

Key takeaways

Powered by Wordpress. Redesign Theme by Robert Toth