Security in the network.
And in the code.
Aviontex builds protection for two levels. AviontexDNS keeps phishing and malware away from your network before a connection is made. Picosegmentation protects software where errors arise: in the code.
Five levels. None replaces another.
We arrange security in five levels, named after the SI prefixes. Each step is finer than the last: from the network through processes and code down to the hardware and the chip. Each level protects something different. A gap on one level is not closed by any other.
- 10−6MicroNetwork and connectionsAviontexDNS
- 10−9NanoProcesses and sandboxesAviontexDNS
- 10−12PicoProgram code: layers and zonesPicosegmentation
- 10−15FemtoHardware
- 10−18AttoChip microarchitecture
AviontexDNS protects your network on the Micro level. Our own DNS servers are secured on three levels: Micro for the network, Nano for the processes and Pico for the code. Femto and Atto lie with the makers of hardware and chips.
AviontexDNS
Before a device opens a connection, it asks for the address of its destination. That is where AviontexDNS checks. If the request leads to an attacker, the device never gets the attacker's address. And because so much is decided at this point, our DNS servers are themselves secured on three levels.
No client
A change to your DNS settings is all it takes. Workstations, printers and IoT devices are protected without installing anything on them.
Encryption stays intact
No proxy, no breaking of SSL. We never see the content of your connections.
Spots attacks early
Not just lists: AviontexDNS recognizes the preparation of an attack and blocks the infrastructure behind it, often before it is put to use.
Servers in Germany
Our resolvers run in certified German data centers. No logging is needed for the service to work.
Picosegmentation
Microsegmentation divides the network into zones. Picosegmentation does the same in the code. Input, processing and output are separate layers. Processing is further divided into zones: a password is handled in a different zone than a simple HTTP call.
An error may sit in its zone. It cannot be used for the effect of another zone, because there is no path to get there.
An effect only arises at a gate in the code.
In practice: AviontexDNS
Our DNS servers are picosegmented. An answer is not true just because it arrived.
Security belongs in the core.
Security by design
Only what is truly needed goes into the system. Every feature that is left out is attack surface that is left out.
Privacy by design
We build so that we cannot see your content. Data we never hold cannot be lost.
Protection without new risk
Security software often runs with the highest privileges in the system. That is why it must be built with the greatest care. Otherwise it becomes the risk itself.