FAQs

Stratus’ new patented technology creates a new server paradigm that revolutionizes the cloud, enterprise systems and communications systems by converting them from static legacy systems to dynamic, on-demand, zero-trust systems that produce enormous security benefits and reduced cloud costs, based on using temporary agile servers.

Stratus’ technology is a new server paradigm that revolutionizes the cloud, enterprise systems and communications systems by converting them from static legacy systems to dynamic, on-demand, zero-trust systems that produce enormous security benefits and reduced cloud costs, based on using temporary agile servers.

A temporary agile server (TAS) is a virtual application server that is created in the cloud, on-demand, with a limited lifespan and accessible only to specific authenticated and authorized users.  The server is loaded with only the software that the specific user needs, and it has access only to the database required for the given transaction.  The lifespan of a TAS is configured by enterprise-defined server termination criteria.  The servers are instantiated with defined operating parameters, server termination criteria and limited to no administrative access.  They are autonomous because once they are created, they cannot be modified in any way: addressed by the control server, any administrator or any unauthorized user.  In addition, they are created with unpredictable IP addresses.

The same as a temporary agile server (TAS)

Our MSP partner will handle the installation and work with you to design and implement your network on the platform so that it is customized for your needs.  They will also train you on the use of the dashboard/control panel operation for both the IT department and anyone needing platform monitoring data.

An IP address is selected rom the available pool of addresses.  The size of the pool will vary from ISP to ISP.  It is not necessary for the IP address to circulate through the DNS system, because the public has no need to search for it.  The server is available on demand to authinticated users.  In most cases, the server will be destroyed and the IP address retired before it has completely propagated through the DNS system.

When using the Stratus Cloud Management System, servers are created on demand and are only available when needed. Consequently, application server time becomes a fraction of what a full-time available system requires, in most cases.  Your aggregated server time on the cloud is much less than it would normally be.  This can result in a 10% to 30% savings.

It has some of the characteristics of a load balancer in that users are sent to different servers, but this is not necessarily based on load.  It may be based on a wide variety of enterprise-defined server termination criteria including a single transaction, a defined number of transactions, a specific time period, a defined volume of transferred data, etc.  In addition, the servers are temporary agile servers that are created random, unpredictable IP addresses.

Yes.  Each application instantiation can be containerized, and any number of containers can be placed on a TAS.

Yes.  This platform works very well with microservices architecture and can strongly enhance the benefits of using microservices architecture.

The latency is less than the natural latency of the internet and is undetectable to the user.

IP addresses are drawn from and returned to a pool of IP addresses, but the method of randomizing and assigning them is proprietary.

The Stratus platform does not control the authentication or authorization functions.  The enterprise’s authorization & authentication functions remain unchanged, and the platform interfaces with the client’s system and databases.  Once a customer is authenticated and authorized, they are directed to a TAS with the proper software instantiation for that customer.

TASs have no administrative controls; therefore, administrative privilege escalation is impossible.  In addition, the attack surface is reduced from 365 days a year for static application servers to whatever server lifespan the enterprise defines.  This could be a single transaction lasting minutes or an IIoT update lasting seconds.  If an attacker does penetrate a TAS, their penetration is aborted when the TAS is destroyed.  Also, the software on the server is from a golden image and is a clean version with no malicious code.  In addition, since the intermediate server in the transaction (TAS) is destroyed after use, there are no files or footprints residing anywhere on the internet that can later be found.

Yes.  Users can be grouped into classes by risk and be given selective access to selected applications and data through a TAS.  The enterprise determines what their risk profile is for their defined user groups or by the sensitivity of their transactions.  The enterprise defines the server lifespan, what and how many users can access a given TAS and application and selects the server termination criteria to match their risk apatite.

Yes.  All other cybersecurity solutions can be used in conjunction with the Stratus Solution, and the Stratus Solution enhances overall cybersecurity.  Cybersecurity applications such as anomaly detection applications can be instantiated on each TAS, and the TAS can self-destruct if an anomaly is detected.

Yes.  The Stratus Cloud Management platform is a multi-cloud platform.  It will work with AWS, Azure, Google and other external cloud providers, in private external data centers, and on-premises behind your firewall.

EC2 provides virtual servers, but the emphasis is on economy of service, whereas Stratus emphasizes better economy of service, much higher security a variety of other functionality.  The Stratus Solution can incorporate EC2 servers and containers, but it has much deeper functionality including dynamic networking, random IP addresses, agile servers and customizable server termination criteria that enable the customer to minimize the attack surface and dynamically control risk.

Logs and details of the transaction will be exported to your specified data server after the transaction is completed but before the TAS is destroyed.  This is controllable by the client through the dashboard/control panel.