SealedWeb Developer FAQs

What is SealedWeb from a developer's perspective?

SealedWeb is information-control infrastructure that developers can integrate into their applications to provide secure information exchange and protection capabilities. Rather than building and maintaining an entire cryptographic security infrastructure independently, developers can leverage SealedWeb's underlying services and integrate information protection into their existing applications.

How can I integrate SealedWeb into my application?

SealedWeb provides API-based integration through its service infrastructure, allowing applications to communicate with SealedWeb services without requiring developers to implement the underlying security mechanisms themselves. The integration approach is designed to keep the application-facing interface straightforward while SealedWeb handles the underlying cryptographic operations and security workflows.

What communication protocol does SealedWeb use?

SealedWeb uses gRPC for communication between client applications and its backend services, and also XMPP for asynchronous communication. These protocols provides a structured, efficient, and strongly defined communication interface for integrating SealedWeb capabilities into different application environments.

Which programming languages are supported??

SealedWeb is designed with cross-platform and multi-language integration in mind. Client-side integration libraries and wrappers are intended to make its services accessible from different development environments. Supported languages and available integration components are documented separately.

Do developers need to implement their own encryption?

Absolultely not! One of the primary objectives of SealedWeb is to abstract the complexity of information protection from application developers. Developers can integrate SealedWeb's capabilities without having to independently implement the entire encryption, key-management, and secure-sharing infrastructure. The entire security infrastructure is transparent to the developer.

How does SealedWeb handle cryptographic keys?

SealedWeb follows a user-controlled key-management model. Private keys are generated and retained on the respective user's device. They are not transmitted to SealedWeb's servers as part of the normal cryptographic workflow. The architecture uses RSA-4096 with OAEP and SHA-256 for asymmetric encryption, together with AES for symmetric encryption. This approach is designed to minimize the exposure of sensitive cryptographic material while enabling secure information exchange between users.

Does SealedWeb use JWT for authentication?

SealedWeb employs its own server-managed authentication and session-management mechanism. Client requests are authenticated against server-side session information, with Redis-compatible infrastructure used for session management. This allows SealedWeb to maintain centralised session control and enforce authentication and authorisation decisions independently of the client application.

Can SealedWeb be integrated into an existing enterprise application?

Yes. SealedWeb is designed to complement existing applications rather than require organisations to replace their existing software infrastructure. Developers can integrate its information-control capabilities into business applications, document-management systems, and other enterprise workflows. The objective is to make information protection an integral part of existing business processes rather than an additional, disconnected activity.

Does integrating SealedWeb require developers to redesign their application's architecture?

No. SealedWeb is intended to function as an integration layer that provides information-protection capabilities without requiring a complete application redesign. Developers can incorporate its services into appropriate points in their existing workflows, allowing information protection to become part of the application's normal operations.

Why should developers choose SealedWeb instead of building their own encryption infrastructure?

Building encryption into an application is relatively straightforward. Building a complete, dependable information-control infrastructure is considerably more involved. It requires careful consideration of cryptographic key management, secure information exchange, authentication, authorisation, lifecycle management, and the handling of information across organisational boundaries. SealedWeb aims to provide this underlying infrastructure so developers can concentrate on their application's business logic rather than continually reinventing security mechanisms. Our philosophy is simple: information protection should be infrastructure, not an afterthought.