As described in our first blog post, Project Mercury is a suite of cloud-native services that simplify the use of verifiable credentials, allowing companies to reduce cost or risk while also enabling better experiences for their users. The next challenge is identifying when or where verifiable credentials can be most effective. In fact, the most frequent question that we get asked is: How do I know if I need a verifiable credential?
Before answering this question, remember that verifiable credentials can be issued by anyone , about anything , and can be presented to and verified by everyone . The entity that generates the credential is called the Issuer . The credential is then given to the Holder who stores it for later use. The Holder can then prove something about themselves by presenting their credentials to a Verifier .
We've created the following infographic to help guide you through the process of determining if verifiable credentials can help you and your business. Follow the flow-chart to determine if you need a verifiable credential and which role your business fits into.
In most cases, businesses are usually either an Issuer or a Verifier. However, in closed ecosystems such as within a single enterprise, it's possible that you'd want to be both the Issuer and the Verifier. This approach can be useful in streamlining processes that span multiple departments/business-units. A common example of this would be a company that issues a verifiable credential attesting to their employment at the company. Other internal services then request proof of employment via a verifiable credential to gain access.
So what are the next steps? If you're interested in simply learning more about verifiable credentials, head over to https://verifiablecredential.io where you can dive into how they work and get your hands dirty in the interactive playground. If you're interested in becoming an Issuer or Verifier, please check out Project Mercury, which makes it fast and easy to do so.
... View more
Wondering if anyone has done this before - read below Requirement - to get to RSA Self Service Portal via a Forti-Web (WAF) using SSL certificates. I would like to know where the SSL certificate have to be loaded i.e. on WAF or RSA Console, and a step by step method that works. Cheers Dana Burton
... View more
Hey I've been working on trying to factor out Semiprimes for the past few months, and I feel like I've definitely found a successful way of Factoring them without a doubt, however, I don't really know anyone, or have any leads to even start when searching for a community based on Computational Challenges and things of that sort. I know you all used to have the RSA Factoring Challenge, which is honestly what I've been trying to simulate basically I guess, but would you all happen to have any ideas or leads for me on where I might be able to find what I'm asking about? Thanks in advance!
... View more
As described in our first blog post about Project Mercury, the vision for Project Mercury is to build a suite of cloud-hosted services to enable companies to utilize verifiable credentials to improve their business. But why? Business interactions are rooted in knowledge. Businesses need to know certain things about their users to provide their services. For example, an employer needs to know the social security numbers of their employees in order to report their salaries to the government; financial institutions are bound by regulation to know their clients to prevent money laundering; businesses need proof of licensure from their staff. But on the internet, how do you really know anything? Credit: Peter Steiner, "On the Internet, nobody knows you're a dog." The New Yorker, 5. July 1993. Bild: PeterSteiner/The New Yorker/The Cartoon Bank Solving this problem is why we started RSA Project Mercury - to allow businesses to truly know their users. As businesses evolve and expand online to achieve global scale, their ability to know is limited. We trust, but we need a way to verify. With verifiable credentials and RSA’s Project Mercury, businesses can finally verify what they need to know. It's now possible for users to collect (cryptographically) verifiable attestations about all aspects of their life, which they can then present to you to enable your workflow. Employees can present digital, verifiable, proof of their social security number; third-party vendors can provide attestations for active employees which can be used to grant access; customers can present claims which attest to their identity allowing financial institutions to achieve compliance with little to no effort; all of which can be instantaneously verified by RSA. Verification creates knowledge, and knowledge is power. What do you need to know about your customers, your employees, or your third-party vendors? Which of your workflows could be transformed to be faster, more user-friendly, and more secure? Leave a comment below to start a conversation with our team. RSA Labs Project Mercury
... View more
Se desideri connettere l'autenticazione RSA al servizio di autenticazione cloud, devi implementare almeno un router di identità. Scaricando e configurando il router di identità integrato per ogni istanza primaria e di replica, puoi evitare il tempo e lo sforzo di distribuire router di identità separati sulla tua rete locale o nel cloud di Amazon análise de site. Il router di identità integrato comunica con il servizio di autenticazione nel cloud e fa quanto segue: Collega il servizio di autenticazione cloud alle tue origini identità. Applica i criteri di accesso, che determinano a quali applicazioni possono accedere gli utenti, quando è richiesta un'autenticazione aggiuntiva e quali metodi di autenticazione sono richiesti. Il router di identità integrato non supporta Single Sign-On (SSO) o RADIUS. Per utilizzare queste funzionalità, è necessario distribuire il router di identità su un'altra piattaforma. Per ulteriori informazioni, vedere Router di identità.
... View more