Skip to end of metadata
Go to start of metadata

Introduction

This document is for administrators, project builders, and integration specialists who integrate Jitterbit with other products, such as Salesforce, NetSuite, and other endpoints. When working with your projects, build with security foremost.

NOTE: Integration Project Methodology contains useful information for an integration project PM. 

Before deploying projects, you should have completed a recent audit of your company’s security infrastructure and procedures. A security audit is a structured, validated evaluation of your company’s information system security. The security audit measures how your company‘s security conforms to a set of established, industry-standard criteria, which include policies, procedures and requirements. 

Security audit and compliance information:

This is not a complete list. Other resources may be available through your organization's security and compliance specialist.

If you operate under any regulatory requirements, such as US FAA or FDA, ensure your security setup is in compliance with these requirements. 

Security and Data Protection Regulations

There are important governmental regulations you may be subject to, depending on where you operate your business or where your customers live and work. These regulations deal with data privacy for which you, along with Jitterbit are responsible. 

The following regulations require Jitterbit, its technology partners, and you to implement and maintain reasonable or appropriate administrative, physical, and technical safeguards. These laws and regulations afford specific privacy rights that you must adhere to. In addition, each has specific reporting timeframes and requirements. 

United States of America State and Federal regulations:

European Union and European Economic Activity Zone Regulations:

  • GDPR (General Data Protection Regulation) gives control to individuals in the EU (European Union) and EEA (European Economic Area). It requires businesses to ensure that their processes that handle personal data must be designed and implemented with safeguards to protect data. These businesses must also disclose their data collection, use, and retention policies. 

Cloud Agents and Private Agents

When you run an integration, Jitterbit connects your data through the agents you configured. Agents can be Cloud Agents or Private Agents and Agents exist in Groups. Groups are sets of Agents in the same Environment, which provide high availability. This means that if one group goes down and is unavailable, another can take its place and continue with your work. Cloud Agent Group is a set of agents maintained and managed by Jitterbit in the cloud. Private Agent Groups are maintained and managed by you, using your own servers or instances within your firewall or hosted virtually on private clouds. By running Private Agents, your sensitive business data will remain within your managed networks.

Which Agent Type to Use?

  • Use Cloud Agent Groups when you want to run your integration in the cloud and you need the scalability that Cloud Agent Groups offer. 
  • Use Private Agent Groups when you want to – or must – run integrations on your premises.

Cloud Agent Groups

Cloud Agents are maintained and managed by Jitterbit. Jitterbit Cloud Agents are multi-tenant and are locked down. Data that flows through is transient and only remains on the agent to complete processing. You can't control or configure the Jitterbit Cloud Agent Group or its agents as you can with your Private Agent Groups. 

When the Jitterbit Cloud Agent Group performs an integration, it connects directly with the application that requires data integration. It then reads and posts data to these applications. If you use persistent storage as part of your project, it will remain on the agent for 24 hours. Data persisting in the Jitterbit Cloud Agent Group is stored in encrypted Amazon S3 buckets that are not directly user accessible. Each integration stores data in its environment’s bucket. For detailed information on Amazon S3 network security and best practices, see Amazon S3 Security

If you have a regulatory requirement that restricts data from residing in the cloud or outside geographic boundaries, use a Private Agent Group instead.

Private Agent Groups

Because you manage and control Private Agents, you control their security. When you use Private Agents, data doesn't leave your servers. If you use a private cloud, you choose where your integration runtime environment operates and you control which network your business data travels and resides in. 

Private Agents authenticate and communicate with Jitterbit Harmony over HTTPS. Private Agents deployed behind corporate firewalls can be configured to communicate via a corporate proxy server. There are no additional networking requirements, such as opening ports within corporate firewalls. Security is your responsibility when using Private Agents. 

Jitterbit provides advice and best practice recommendations for hosting Private Agent code in System Requirements for Private Agents.

NOTE: If you are using private agent groups, review the information under Security and Data Protection Regulations.

Securing Endpoints with Private Agents

There are many methods you can use to secure endpoints including:

  • Use a VPN (Virtual Private Network) along with encryption.
  • Network whitelists can control who is allowed access to your network. To use whitelisting with Private Agents, see Whitelist Information.
  • Make sure any drivers and plugins you use are up to date and tested. 

Organizations and Environments

Different users and groups will need different access levels to access your Organizations and Environments.  A user doesn't need the same access level as a developer or an administrator. For example, a developer in your organization may need Execute and Write permissions to the API Manager to create and edit security profiles, create and edit APIs, and access certain functionality in Management Console. The day-to-day user doesn't require these elevated permissions. Think about users and groups and what they do. Limit access so that users can only use what they need to perform their tasks. 

NOTE: For information on the different access roles, such as User, Administrator, and Developer, and how to define them, see Managing Role Access to Environments on the Environments page. 

Apply hardware and software patches. For Cloud Agent Groups, Jitterbit is responsible for code changes. If you are using Private Agent Groups, monitor updates and patches to your OS and application software, drivers, and plug-ins, and apply them when appropriate.

Providing secure authentication using OAuth and multi-factor authentication, such as 2FA (two-factor authentication) is critical. OAuth is discussed under Security Profiles in the API Manager. 2FA is discussed in Jitterbit Password Controls.

Keep development and testing accounts separate from production. This includes separate IDs and passwords. Remove these development and testing IDs and passwords before migrating code to production. Instead, use project variables to store information such as IDs and passwords. As a best practice, maintain separate development, testing, and production environments. You should also ensure that Personal Identifiable Information (PII) is not used in testing. 

NOTE: If you are in a regulated industry, such as health care, or if you are subject to government regulations concerning data and data movement, review those requirements as part of your security planning.

API Security

NOTE: For an in-depth discussion on the Harmony API and Security, see Harmony API Security.

The Harmony API Manager supports OAuth 2.0 authentication with Google, Okta, and Salesforce as Identity Providers. NetSuite now enforces token-based authentication (TBA) for Administrator, Full Access, and other highly privileged roles as of their 2018.2 release. See NetSuite 2018.2 Token-Based Authentication for more information and instructions. API Keys and API Secrets can be used to authenticate users with the Harmony API. 

Certificates

Jitterbit can authenticate with external resources with SSL client certificates when connecting to HTTP or SOAP endpoints in Cloud Studio, and with HTTP endpoints or Web Services in Design Studio. Client Certificates settings can be accessed in the Jitterbit Harmony Portal on the Management Console > Customizations > Client Certificates page. 

Adding Certificates to a Keystore 

Jitterbit applications that are installed locally include a trusted keystore that contains the certificates needed for secure communication via HTTPS. For example, you would add a new certificate to the Jitterbit Java keystore if you use a proxy server and need to allow the Jitterbit local client to securely communicate through the proxy server. You can add new certificates as needed. You will also need to replace or renew certificates if they are changed. Information and instructions on adding certificates to a keystore can be found on these pages:

Connector Security

When migrating your project to another environment, you want to avoid sharing private information. Start with these connector security features:

  • Project Variables: When working with Connectors, project variables can provide additional security. If you're creating scripts or transformations, use project variables for private information such as login or user IDs, passwords, access keys, and other information that must be kept secure. See Using Project Variables in Scripts or Transformations for information and procedures. 

  • Configuration: Unencrypted user names and passwords are required at runtime. Use keystores and pull this information from a database stored off the agent and not called until runtime. 
  • Third-party Vaults: Secure, digital online vaults are designed to protect the privacy of your data. Using data encryption, strong user authentication, and redundant storage, these vaults allow cloud storage with data security. The specific features, pricing, and instructions depend on the provider you choose. 
  • IP Whitelists: In most situations you don't need to make any special network or firewall changes when Private Agents or Design Studio communicate with Jitterbit Harmony. What if your network is behind a firewall? In that case, configure your network to communicate with Jitterbit Harmony and use a whitelist to allow this communication. Jitterbit provides whitelisted IP addresses for each region. See Whitelist Information for more information. 

Log Security

When thinking about logging and security, examine your business requirements. Decide on what level of logging you need and what risks are acceptable to you based on your security requirements. Jitterbit generates logs for different functions such as operations logs, Windows or Linux event logs, and API logs. Most customers use cloud logging in the Jitterbit cloud. Log data is encrypted for security. You can disable cloud logging if required.

NOTE: If you disable cloud logging, application logs are not written. 

Cloud Agents

When a Cloud Agent Group runs an integration operation, it creates an activity log which is stored in the cloud. You view logs in Cloud Studio from the Activities tab in the Management Console. Log records are retained for 30 days, but the details are retained for 5 days. Jitterbit supplies logging and error functions to help you create and debug scripting. WriteToOpereationLog() can be used to write sensitive data to logs, but we strongly recommend against this as it can create a security issue. 

Jitterbit provides a Jitterpak with an API you can use to download your logs. This Jitterpak is available from Jitterbit Support. Click Submit a Support Case under Quick Links in the side bar to request this Jitterpak. Contact Jitterbit for information on the retention schedule for log data. 

NOTE: Jitterbit does not provide native support for sharing Cloud Studio logs using ELK, Splunk, or Loggly. 

Private Agents

Using a Private Agent Group keeps all your information within your organization and on your own servers. Disable cloud logging, to avoid sending logs to Harmony. At the end of each operation, you can use a script to send log data locally. Debug logs, transformation logs, error logs, endpoint call error logs, and more are available, and can be set in the jitterbit.conf file.  See Editing the Configuration File - jitterbit.conf for settings and values. 

On This Page

Last updated:  Feb 07, 2020

  • No labels