As a cybersecurity professional tasked to protect every digital asset to the best of your ability…
Until now, you’ve only had some form of Container-Related Asset Protection, focused on protecting the container (whether it be a browser, operating system, database, spreadsheet, document, file system, server, server farm, or cloud) upon which the digital asset was completely dependent for its protection. This is much like having to defend every individual egg in a basket from a skulk of foxes, with nothing more than a chain cobbled together from a set of disparate solutions, all derivatives of historically failed approaches to providing security.
Failed technologies dominating the headlines
Every link in the security chain is dependent upon some form of encryption. But encryption has serious issues no one wants to discuss, including the fact that all things encrypted must be decrypted somewhere for use, and all the fox has to do is wait and grab the eggs from where they are decrypted, rendering encryption meaningless (once decrypted, the protected asset can be copied anywhere in its unencrypted form). Traditional encryption has back doors provided by the vendors to most major governments (and known to hackers), and suffers from locked relationships – the source, results, and key(s) all are fixed in relation to one another such that if you know any two of the three, you can easily determine the third. Most hacks are made even easier because keys are stored (intentionally or through ignorance) where they are accessible to someone (including employees), or are even transmitted over networks prior to, or during, use.
Naked and afraid all by themselves, the eggs are dependent upon the basket for all of their protection, and cannot leave the basket safely. If the basket is broken into, dropped, or stolen in its entirety, the eggs are defenseless and helpless.
The basket itself has no intelligence – it knows nothing of the eggs within it or of the security provided to it, or even that it needs external protection.
The security provided for the basket protects only the basket and knows nothing of the eggs in it – once an egg is outside the basket being protected, the basket security could care less. The chain of basket security is only as strong as its weakest link, and it has many weak links.
Links are provided by different products from different vendors, each to a different standard, and each requiring that its unique implementation be done perfectly if it is to have any strength. Links are made of quickly-decaying materials, and each must be individually maintained and updated. Any one missing, broken, or open link invalidates all security.
AMULET™ Technology Approach
The AMULET™ framework is free and available to any intelligent device that wants to support AMULET™ security for an egg. The framework provides a unique safe haven into which each egg is automatically deposited upon arrival. The framework interprets its host environment for the egg, communicates with the outside world on behalf of the egg, and manages relationships between eggs. The framework’s most important role is to determine from the AMULET™ criteria embedded into the egg whether it is safe to temporarily expose to a trusted requestor a limited view
AMULET™-protected eggs are always in their enciphered (locked) state, even when a temporary unenciphered view is being rendered to a trusted requestor. This approach is referred to as “fail-safe”, meaning that even when bad or unexpected things happen, the egg is always safe.
Note that we use the term “enciphered”, not encrypted – we use a proprietary patented means of enciphering digital assets that can include encryption, but is not limited to encryption (or to a singular method of any kind). You may notice that even when the same egg is enciphered on the same device at the same time in multiple iterations, no two iterations produce the same results – the resulting files aren’t even the same size. There is no fixed relationship between source, result, and key as there is in traditional encryption. Nor is there any human interaction in the generation, seeding, storage, or even awareness of any keys.
It might surprise you to learn that even if you hacked our system and discovered something that appeared to have the role of a key, entering the stated value of that entity would always result in failure. It would certainly confuse you that a brand-new device and AMULET™ framework with no Internet connection can safely and reliably access any egg downloaded by another device. You might wonder how it is the operating system has no record of the medium to which an egg is being temporarily deciphered, and from whence the unenciphered contents are being dispensed.
Whether or not the specific details of what we have accomplished interest you, you can be assured that we have invested thirty-five years analyzing the practical implementations of cybersecurity technologies deployed in the wild, and for every weakness discovered, devised one or more solutions. We are the only cybersecurity vendor on Earth whose first and primary focus is actually on security, rather than upon making a profit by any means necessary. We discovered long ago that the most important step in ensuring the safety of eggs is to get the relationship of the delivery cart and the horse in the proper order.
AMULET™ egg protection offers phone-home communications whenever a network is available to either the AMULET™ framework or the egg (and when not available, store-and-forward capability until and when connectivity becomes available). Phone-home features initiated by the egg or framework include hysteresis and activity reporting for audit trailing, update requests, and real-time unauthorized activity intervention.
Communications support also includes externally-initiated conversations from the egg owner or maker which can include dynamic real-time updates of the egg or AMULET™ framework, or changes in assigned AMULET™s and/or assigned AMULET™ criteria.
AMULET™s bring with them a backpack full of helpful defenses and adaptations, called criteria, that help the egg deal with any environment or situation the egg finds itself in, all perfectly suited to the egg’s mission by the mission’s commander (the author of the intellectual property contained inside the egg).