We at Web3 Enabler are committed to simplifying the creation and management of Salesforce web3 security policy for real businesses, across multiple industries.
Some Challenges of Traditional Corporate Security Policy
I recently conducted an X poll asking fellow cybersecurity professionals which of the following compliance requirements pertaining to login credentials receive the most pushback from clients or employees upon enforcement. The responses included a combination of the following.
- Use of password manager
- Password length
- Password rotation (requiring that users of a system update a password when there is evidence that it’s been compromised)
- Other
There is greater room for potentially costly pushback when the credentials management best practices are not explicitly recognized as compliance requirements.
It can be even more challenging to address these challenges with web3 login credentials for various users within an organization than it is for web2 login credentials. This may be the case for a combination of the following reasons.
- Self-custody security recommendations might not make sense for businesses: For example, certain web3 wallets’ documentation includes recommendations, such as storing seed phrases offline. However, that does not make sense for users across an entire organization or organizational unit, because more than one user may need to access a corporate wallet.
- Difference types of credentials: Users of web3 wallets cannot update the private keys or seed phrases associated with those wallets.
Salesforce Web3 Security Policy
Web3 Enabler empowers corporate users with simple to learn and use security features, including but not limited to the following, directly in Salesforce.
- Compliance automation integrations that simplify organizations’ security operations workflows.
- Management of information about Org Wallets and Account Wallets
Guidance around the use of these features are outlined in our Salesforce Blockchain Payments user guide.
