Security best practices

DFNS provides multiple layers of security to protect your organization. This guide covers best practices for:

• Roles: Control who can do what
• Policies: Enforce rules on transactions and sensitive operations
• Address book: Protect against address poisoning attacks
• Verified assets: Filter out spam tokens and suspicious transactions

​

Getting started safely

Before creating wallets or processing transactions, set up these foundational security controls.

​

Initial policies

To create these policies, go to Org > Policies and click New Policy. Select the appropriate activity type and configure approval groups to require at least a 1-out-of-2 quorum.

​

Initial role setup

Follow the principle of least privilege: give users only the roles they need for their responsibilities. See role templates below for recommended configurations.

​

Policy templates by use case

​

Treasury management

For internal teams managing company wallets with multi-signature approvals:

​

Exchange/trading operations

For high-volume operations with exchange integrations:

​

B2B payments

For business payments and vendor disbursements:

​

Role templates

Create these roles in Settings > Permissions and assign them to users based on their responsibilities.

​

Admin

Full organizational control. Assign sparingly. You can use ManagedFullAdminAccess for this role. The list of whitelisted actions is maintained by DFNS and contains all permissions.

​

Approver

Reviews and approves transactions. Cannot initiate them.

​

Operator

Day-to-day transaction operations.

​

Read-only auditor

View-only access for compliance and audit purposes.

​

Service account (automation)

For server-to-server API integrations. See service accounts guide.

​

Using the address book

The address book helps you manage blockchain addresses with human-readable aliases. Beyond convenience, it provides critical protection against address poisoning attacks.

​

Address poisoning protection

In transaction history, the dashboard shows warnings for addresses not in your address book. This protects against “address poisoning” attacks where scammers:

1. Send tiny transactions from addresses that look nearly identical to legitimate ones (e.g., 0x1234...5678 vs 0x1234...5679)
2. Hope you copy the wrong address when making your next transfer

Best practice: Add all addresses you regularly interact with to the address book immediately after your first transaction.

​

Address book management

• Use clear naming conventions: Include vendor/partner name, purpose, and network (e.g., “acmecorp-payroll”)
• Add descriptions: Note the business relationship or account purpose
• Review regularly: Remove aliases for addresses no longer in use
• Update promptly: Add new addresses as soon as you establish new business relationships

​

Address book vs policy whitelisting

These are complementary features:

• Address Book: Visual convenience and warnings. Helps you recognize addresses in the UI. Does not block transactions.
• TransactionRecipientWhitelist policy: Enforcement. Blocks transactions to non-whitelisted addresses (or requires approval).

​

Handling spam and scam tokens

Blockchain addresses can receive unsolicited tokens (airdrops, spam, scam tokens). DFNS provides tools to filter these out.

​

Verified assets and transactions

On each wallet page, use the filtering toggles to focus on legitimate assets: Assets section:

• Toggle: “Only show verified assets”
• The “Verified” column indicates which tokens are verified by DFNS

History section:

• Toggle: “Only show verified transactions”
• The “Verified” column shows transaction verification status

​

What “verified” means

• DFNS maintains a list of verified tokens and contracts across supported networks
• Verified: Token is a known legitimate asset
• Not verified: Token is not in DFNS’s verified list (doesn’t necessarily mean malicious, but warrants caution)

​

Incoming transaction screening with Chainalysis

For additional protection, integrate Chainalysis KYT to automatically screen transactions:

• ChainalysisTransactionPrescreening: Screen outbound transactions before signing
• ChainalysisTransactionScreening: Flag incoming transactions from suspicious addresses

​

Day-to-day security operations

​

Reviewing pending approvals

When policies trigger approval requests:

1. Go to Activity in the dashboard to see pending approvals
2. Review the transaction details, including recipient address and amount
3. Verify the recipient is in your address book or is otherwise expected
4. Approve or reject the request

​

Monitoring transactions

• Check the “Verified” column in transaction history
• Enable webhooks for real-time notifications
• Export transaction history for compliance records (Wallet > Export)

​

Regular security hygiene

​

Next steps