Frequently Asked Questions

What Is Polymorphing for Linux?

How is Polymorphing for Linux different from ASLR?

What versions of Linux do you support?

How often are the packages in your repositories re-scrambled and updated?

What is the meaning of “Polyverse”?

What is Polyverse, and what does Polyverse do?

Who are your main competitors?

Is Polymorphing for Linux effective?

How does our custom compiler compare/differ from the stock compilers being used to build our supported Linux distributions?

Does Polyverse give me logs/metrics/data?

How do I get started?

Do you have documentation, videos, demos?

Can you share an example of a breach that could have been prevented through Moving Target Defense?

Can pre-compiled binaries be scrambled on Windows?

Do we need to recompile to take advantage of Polymorphing for Linux?

Which languages are supported?

If you do not know the hashes of a binary ahead of time, then how will you be able to verify that the binary has not been modified by a malicious party?

Do you provide modified binaries for ElasticSearch's ELK stack (elasticsearch, logstash, kibana)?

Why is this solution better than existing ones?

What do you guys really stop?

Is Polyverse licensing per VM that will use the packages? What about “dev” VMs? Is it only for production VMs that are shipped?

Polymorphing for Linux is too complex—we don’t want to use compilers and have to compile everything. Is there an easier way?

What if the solution is implemented on an isolated company network? How will the licenses will work? Will there be any offline updates?

How does a Polyverse’s scrambling technology differ from out-of-the-box memory, page, and sysrq kernel protections?

Can you debug Polymorphed binaries?

Can you debug Polymorphed kernels?