Blogs

Secure Your Integrations with Fluxygen Hardening

Default Allow or Default Deny: Which Is Right for You?

Your business processes increasingly rely on a combination of systems, applications, and data. Fluxygen ensures that these systems communicate reliably with one another. But how do you prevent unauthorized parties from gaining access to your integrations?

To address this, Fluxygen offers the hardening concept: an extra layer of security that, by default, blocks unknown traffic from your Fluxygen environment. Only systems, applications, or parties that you explicitly authorize in advance can connect.

From publicly accessible to controlled access

In the default configuration, Fluxygen is accessible via the public internet. That doesn’t mean anyone can just access your environment: users log in with their own credentials and two-factor authentication. You can also add an extra layer of security to integrations and endpoints with authentication.

This open architecture offers great ease of use. New external systems, vendors, customers, or services can connect to your flows relatively easily. This is practical when you work with parties that use changing or dynamic IP addresses.

Do you have higher security requirements? Then there’s a stricter option: Default Deny.

With Default Deny, incoming traffic is blocked by default at the network level. Only pre-approved IP addresses are granted access. This means the check takes place before a request even reaches the Fluxygen application or a specific flow.

This provides an important additional safety net. If the authentication for an inbound HTTP flow were ever configured incorrectly, the network layer would still prevent unauthorized traffic from reaching your environment.

What does hardening mean for you?

Hardening makes your Fluxygen environment more resilient against unwanted external access. The basic principle is simple: grant access only to systems and parties that actually need it. This aligns with the least privilege security principle.

In practice, this means:

  • Only known IP addresses are allowed to connect to your Fluxygen environment.
  • New external systems or partners are added to the allowed list in advance.
  • Unknown traffic is automatically blocked.
  • Your existing flows do not need to be modified.
  • The additional layer of security is applied before the standard Fluxygen authentication and before any security measures you set up yourself within a flow.

 

This allows you to retain the benefits of a cloud-based iPaaS platform—such as monitoring, updates, support, and scalability—while gaining more control over who can access your integration environment.

Additional Security with a VPN

Do you work with systems located within your own corporate network, such as an on-premises ERP system, database, or production application? If so, you can connect Fluxygen via a VPN connection.

A VPN creates an encrypted, secure connection between your internal network and your Fluxygen environment. This allows systems within your organization to communicate securely with Fluxygen without that connection needing to be publicly accessible via the internet.

The combination of a VPN and system hardening is the most securely protected configuration that Fluxygen currently offers:

  • Your internal systems communicate via a secure VPN tunnel.
  • Incoming internet traffic is blocked by default.
  • Only explicitly authorized external IP addresses can connect, if necessary.
  • Fluxygen remains available as a managed cloud platform, including service, monitoring, and ongoing development.

 

When is Default Deny right for you?

Default Deny is particularly suitable if you know in advance which systems, partners, or service providers need to connect to your Fluxygen environment. Think of a fixed set of suppliers, customers, ERP systems, databases, portals, or EDI partners.

Situation

Most Appropriate Configuration

You work with many external systems with varying IP addresses

Default Allow, supplemented with strong authentication in the flow

You have a fixed group of known systems and partners

Default Deny with IP allowlisting

You integrate with internal, on-premises systems

VPN connection

You have high requirements for control and security

Default Deny combined with VPN

You use Fluxygen as an internal integration hub

Default Deny, possibly supplemented with a VPN

Hardening does require a minor organizational step. Are you setting up a new external connection, or has a partner’s IP address changed? Then this must be coordinated and added in advance. On the other hand, you maintain control over access to your integration landscape.

Secure integration while maintaining control

Security and ease of use always require a careful balance. Do you work with a clear, familiar set of systems? Then hardening is a logical choice. You limit access to only what is necessary, without compromising the stability, performance, and flexibility of Fluxygen.

Want to know which setup is right for your integrations, external partners, and security policy? The Fluxygen team would be happy to work with you to find the right combination of network security, VPN, and flow authentication.

Contact us for a no-obligation consultation about “hardening” your Fluxygen environment.

Recent resources

Fluxygen 4.17.13

Fluxygen release 4.17.13 focuses on security, s...

Cybersecurity and Updates

How can an iPaaS provider manage cybersecurity,...

Application Integration is more than an API Connection

An API connection alone does not make a success...

Secure Your Integrations with Fluxygen Hardening

Fluxygen hardening adds an extra security layer...

This website uses cookies

We use cookies to personalize content, provide social media features, and analyze our traffic. We also share information about your use of our site with our analytics partners. You can change your preferences at any time. For more information, please see our Privacy Policy and Cookie Policy.