ACCOUNT SECURITY

Compare custodial account security controls

Compare sign-in, withdrawal and recovery controls using product-specific documentation, clear exceptions and a practical evidence checklist.

Prepared with AI assistance and approved for publication by CryptoTrades November 15, 2026. Public documentation and the synthetic example were checked; no account testing or independent security review is claimed.

Start with the account and the task

Write the provider, product, account region and interface at the top of your worksheet. An exchange account, a consumer app and a self-custody wallet can have different recovery and authorization paths. A feature documented for one product should not be assumed available on another.

Then separate four tasks: signing in, approving a withdrawal, changing settings and recovering access. Ask which task a control covers. A strong sign-in method is not evidence that withdrawal changes use the same method or that recovery cannot bypass it. If the documentation does not answer a question, record “not verified” rather than guessing.

Never put passwords, recovery codes, identity documents or complete account details in this worksheet. It should describe controls, not contain the secrets that operate them.

Evidence:

Compare the documented controls

The table compares documented mechanisms. It does not establish that a control is enabled, works in every account or prevents every compromise.

Documented account controls; no account functionality tested
QuestionCoinbase consumer documentationKraken documentationWhat to verify yourself
Sign-in and backupCurrent 2FA guide offers multiple methods and backup combinationsGSL setup guide asks users to configure sign-in 2FA before locking settingsAvailable methods and enabled fallbacks in the exact account
Withdrawal destinationsConsumer allowlisting limits sends to address-book entriesGSL description includes blocking addition of crypto withdrawal addressesExisting destinations, change authorization and notifications
Waiting periodsConsumer guide describes a 48-hour address wait and disable delay, with an early-disable exceptionGSL setup guide describes a chosen unlock period and Master Key overrideWhen a timer starts, exceptions and who can bypass it
RecoveryDocumented backup methods require planningA previously configured Master Key can immediately remove GSLStorage separation and the consequences of losing recovery access

Evidence: Coinbase consumer 2FA · Coinbase consumer allowlist · Kraken GSL setup · Kraken GSL scope

Product names matter more than a brand-wide checkmark

Coinbase's consumer allowlist page describes a 48-hour wait for a new address and for disabling allowlisting, with an exception when disabled within eight hours of activation. Its separate Global Exchange page describes a different activation pattern: no delay to enable and 24 hours to disable. Do not combine these rules into one “Coinbase waiting period.”

Evidence: Coinbase consumer allowlist · Coinbase Global Exchange allowlist

Read the override before relying on the delay

Kraken's GSL setup guide says to configure sign-in protection and a Master Key first, because those settings cannot be added or changed while locked. A previously configured Master Key can remove the lock immediately. The setup page gives a selectable waiting range of 1–29 days and a three-day default; confirm the current interface rather than treating this guide as setup instructions.

The practical question is whether the recovery route shares a failure point with everyday sign-in. Kraken recommends keeping the Master Key on a different device. A long timer alone does not describe protection if an attacker also has the override. Conversely, losing the override can make a legitimate user wait. This tradeoff belongs in the comparison.

Evidence: Kraken GSL setup · Kraken GSL scope

Worked example: count evidence gaps, not safety points

Consider a fictional worksheet with six questions: sign-in, fallback, destination changes, delay exceptions, API permissions and recovery. Suppose three answers have current documentation, one source applies to the wrong product and two are unanswered. The usable evidence count is 3 out of 6, or 50%.

That percentage measures worksheet completeness only. It does not mean the account is 50% secure, that three controls are equally valuable or that another provider with more documentation is safer. The wrong-product answer remains unverified until replaced with applicable evidence. The example contains no observed customer records or compromise probabilities.

Evidence:

Finish with a reviewable record

Save one row per control with its scope, source URL, date checked, known override and unanswered questions. For API access, ask about permitted actions and revocation; this article has not verified either provider's current API settings. Record that gap explicitly.

Revisit the worksheet after a recovery change, device replacement or provider notice. Use official support channels reached from a bookmarked provider site for account-specific questions. No account was accessed, configured or tested for this comparison.

Use the exchange checklist for broader research. The fee comparator answers a separate cost question using editable percentage assumptions; it does not measure account security. No financial inputs, credentials or account connections are needed for this worksheet.

Evidence:

Sources & method

  1. Coinbase consumer 2FA

    Provider documentation refreshed before publication. Exact product, region, enabled account settings and recovery exceptions require verification; no effectiveness test performed. Checked 2026-11-15.

  2. Coinbase consumer allowlist

    Provider documentation refreshed before publication. Exact product, region, enabled account settings and recovery exceptions require verification; no effectiveness test performed. Checked 2026-11-15.

  3. Coinbase Global Exchange allowlist

    Provider documentation refreshed before publication. Exact product, region, enabled account settings and recovery exceptions require verification; no effectiveness test performed. Checked 2026-11-15.

  4. Kraken GSL setup

    Provider documentation refreshed before publication. Exact product, region, enabled account settings and recovery exceptions require verification; no effectiveness test performed. Checked 2026-11-15.

  5. Kraken GSL scope

    Provider documentation refreshed before publication. Exact product, region, enabled account settings and recovery exceptions require verification; no effectiveness test performed. Checked 2026-11-15.

Continue learning

Found an error? Contact the editorial team with the page and supporting source. Never send private account information.