Frequently Asked Questions
We understand you may have questions regarding the P55 Dynamic Security Platform, the P55 DynaKey API Key platform, and InnoviGuard. Here we offer answers to the most commonly asked questions. We are always happy to answer any other inquiries you may have including questions on how we can demonstrate the power behind both the P55 and P55 DynaKey platforms.
P55 Dynamic Security Platform
1 - How does the P55 generate dynamic hashes?
The P55 algorithm is a groundbreaking innovation in the realm of dynamic hash creation and verification. Its core is built on decades of research and has been scrutinized by top universities in the world. Exactly how the P55 technology works will remain a closely guarded secret.
2 - Can the P55 hash be brute-forced?
No, the P55 hash cannot be brute-forced. It is designed with advanced security measures that make such attempts infeasible. However, there is a nuanced aspect to consider: while the hash itself is immune to brute-force attacks, its security relies on the specific context in which it was generated.
Each P55 hash is tied to a unique configuration, ensuring that even if hashes are exposed during a data breach, they cannot be brute-forced without access to the specific environment that created them. This inherent uniqueness prevents attackers from using generic tools or setups to compromise P55 hashes, making brute-forcing practically impossible.
3 - How do you know that the P55 hash is Quantum-Resilient?
This has not been tested yet, but considering how the P55 hash is calculated, it SHOULD be resistant. We welcome any and all attempts to prove us right or wrong.
4 - Why do we not adhere to Kerckhoffs's principle?
The answer is simple: we’re not reinventing cryptography. P55 isn’t about creating a new cryptographic algorithm; it’s about building on the solid foundation of existing ones. For example, we’ve openly stated that SHA512 and/or Blake3 plays a role in our solution, but that’s just one piece of what makes P55 unique.
Think of it like cooking. Just as chefs use familiar ingredients to create something entirely new, we blend proven cryptographic methods in a way that’s unique to us. While we mention SHA3512 or Blake3, much like a recipe listing chicken, the real magic is in how we combine these elements — our secret sauce, if you will, similar to KFC’s famous recipe. That’s why you won’t see SHA3512 or Blake3 in our branding; they’re just part of the mix behind the P55 technology.
If we’d developed an entirely new cryptographic algorithm, we’d have leaned more into Kerckhoff’s principle. But with our current approach, it’s not a necessity.
Also, take a look at the answer to “Is P55 DynaKey using a cryptographic hash?”
5 - But static hashing algorithms doesn't always generate static results. What about salt and pepper?
The essence of static hashing algorithms lies precisely in their static nature. By definition, they produce consistent outcomes. Even when incorporating a salt, the resultant hash remains static; altering the salt for every instance necessitates storing it, which does not fundamentally alter the vulnerability of the system. The equation of salt+password equating to a static hash underscores this limitation.
P55, on the other hand, eliminates the need for either salt or pepper. Its design inherently embraces dynamism, distinguishing it from the superficial variability introduced by salt and pepper.
P55 DynaKey API Key Platform
1 - Does P55 DynaKey save anything?
No. The system is completely self-contained and only needs enough space for logs.
2 - Is P55 DynaKey complicated to set up and use?
The short answer: No.
The long answer: Still no, and here’s why.
P55 DynaKey doesn’t require you to store anything new in your database. Instead, it dynamically generates and verifies keys on the fly, eliminating the need for traditional static hashes. Integration is straightforward, as P55 DynaKey operates as a lightweight addition to your existing infrastructure, requiring minimal configuration.
Users won’t notice any changes in how they interact with your system, but you’ll have the confidence of knowing their authentication is backed by state-of-the-art dynamic security. No complex setup, no extra database overhead—just better security, seamlessly delivered.
3 - Is P55 DynaKey using a cryptographic hash?
No, it’s not a cryptographic hash. At its core, it has cryptographic algorithms that have been tested and tried by world-leading universities and cryptologists around the world such as SHA3 512 and Blake3.
4 - What are the requirements for P55 DynaKey?
In short, Linux. You can either run it as a daemon or use our convenient Docker container. The hardware depends on the number of simultaneous generations and verifications. We have successfully tested P55 DynaKey on a Raspberry Pi 4 and could create a few thousand P55 hashes per second.
5 - How do I get P55 DynaKey?
By contacting us. For now, we build each Docker container or daemon manually. You can reach us at sales@innoviguard.com.
6 - Where can I download the P55 DynaKey libraries?
By contacting us at sales@innoviguard.com.
7 - Can I have a demo license to try it out?
Contact us at sales@innoviguard.com. Let’s see what we can arrange.
8 - This sounds too good to be true. Does P55 DynaKey really do everything you say it can?
Though a statement and a question, we hear this a lot. The short answer is yes. P55 DynaKey really can do everything we say it can and we are ready to back that up through a demo and even a test period where we challenge you to throw everything you can at the platform and see if you can break it.
100’s have tried. On a one, yes ONE character password. None succeeded.
Reach out to us today at sales@innoviguard.com and we’d be happy to book a demo meeting and talk more.