Modern businesses depend on a collaborative ecosystem of partners, suppliers and customers. Financial services, logistics, health care, smart city, risk management, asset tracking, surveillance and other enterprise services provide valuable business information that must be shared within this ecosystem.
Much of this information is either transmitted or received as a continuous stream, where incoming data is processed as subsequent information arrives. Unlike “request/response” (synchronous mechanisms where an application makes a request and waits for an answer), the streaming, asynchronous model sends data to requestors whenever data is ready to send. For high-performance enterprises who often have requirements for high-speed, mission-critical applications, the streaming model provides an efficient base on which to build their production-ready services.
However, many of these streams naturally must cross many organizational and firewall boundaries across the globe. They also must be available to any type of computing device from desktop to mobile or embedded devices.
And most importantly, streaming services must be secure.
Security is central to the design and implementation of our application connectivity products. We have invested tremendous amounts of resources to ensure our customers can extend their streaming services securely to their customers and partners without sacrificing performance and without adding complexity to their architectures.
A key technology in our foundation is WebSocket, an industry standard since 2011. Our co-founders were instrumental in the development of this formal standard. WebSocket offers a “fat-pipe”, cloud-friendly connection leveraging the ubiquitous Web that connects all devices and services on the planet. However, that standard alone is not enough to build and deploy production-hardened environments. We have added many features that enhance security for application-to-application connectivity.
Here is a list of 10 cool things about Kaazing's secure streaming. For a detailed deep dive into each of these points, download our free whitepaper.
WebSocket connectivity is only as secure as its implementation, which is needed in multiple languages and operating systems.
Legacy solutions connect at a very low-level, with wide-open access, which opens up a potential security vulnerability. Kaazing connectivity is defined at the application-level, providing tighter security and deployment flexibility.
Deploying business logic in the DMZ is potentially insecure, and if exposed could be crippling to your business. Our streaming product is application-stateless and can be easily daisy-chained and deployed in multiple DMZ layers so your business assets stay well protected behind layers of firewalls.
Network ports that remain open listening for connections are prime targets for hackers. Our streaming product can be configured so 100% of all incoming ports are closed hiding all internal sensitive information.
Transparent reconnection is essential for dependable security. This is especially true on unreliable networks where disconnections can occur or when network hardware may terminate long-lived connections.
A variety of pluggable, fully-tested encryption algorithms provides selectable encryption strengths without having to change any code.
It is mandatory to validate users and applications using a single source of authentication and entitlements. We provide integration points in our streaming product for SSOs and enterprise ACL subsystems.
Various fallback strategies when WebSocket is not available in browsers must not compromise security. We implemented CORS for legacy browsers to always maintain consistent cross-site security.
Injection of insecure code is detected immediately and rejected.
Offers clustering for local and remote reliability, essential for production.