Method

How findings are prioritised

Not every quantum-vulnerable setting is equally urgent. A key exchange that protects health records is a bigger problem than one that protects a session cookie, even if the cryptography is the same. QuantumShield ranks every finding by what is at stake in your org.

Harvest now, decrypt later

An attacker does not need a quantum computer today to steal today's data. They can record encrypted traffic now, store it, and decrypt it once a quantum computer can break the key exchange that protected it. So the question is not "when will quantum computers arrive?" but "will this data still matter when they do?"

The test

If the left side is bigger, you are already late: data sent today will still need protecting after it can be read. The difference in years is the finding's margin.

Signatures and certificates are different: a recorded signature cannot be "decrypted later". For them only the fix time counts, because the replacement must be in place before forgery becomes possible.

Where the numbers come from

How long the data must stay secret

The scan reads, from metadata only and never from records:

  1. Your field classification. Salesforce's Data Sensitivity Level (Restricted and Mission Critical count as long-lived regulated data) and Compliance Categorization (PII, GDPR and CCPA count as personal data; HIPAA, PCI and GLBA as long-lived regulated data).
  2. Shield Platform Encryption. Fields you chose to encrypt count as at least confidential, and decide what each Shield key protects.
  3. Best-practice defaults for standard and industry objects that exist in the org, when nothing is classified (table below).

An integration is assumed to carry the most sensitive data found in the org. You know better: open a finding in the app and say what that integration really carries. Salesforce only shows fields the scanning user can see, so treat the profile as a lower bound.

How long the fix takes

Each rule states the effort of its fix. By default low effort takes 1 year, medium 2 years and high 4 years, including testing and coordination with partners.

When a quantum computer can break it

Nobody knows. QuantumShield assumes 2033 by default and offers 2030 (conservative), 2033 (moderate) and 2035 (optimistic) presets. NIST plans to deprecate today's public-key algorithms after 2030 and disallow them after 2035 (NIST IR 8547). Change the year in the app and the ranking updates instantly.

Default assumptions

All of these can be changed in the findings view. Your changes stay in your browser.

DataStays secret forExamples
Long-lived regulated25 yearsHealth, national identity and financial-account data that stays sensitive for decades.
Personal data10 yearsNames, contact details and other personal data covered by privacy law.
Confidential business7 yearsContracts, pricing, pipeline and financial records kept for audit.
Internal3 yearsOperational data with little value to an outsider after a few years.
Short-lived0 yearsSession tokens, one-time codes and data that is worthless within months.

Worked example

A named credential sends Contact records, which include a national ID number classified as Restricted, to a partner over TLS. Salesforce callouts still agree their keys with classical cryptography. The data must stay secret for 25 years and the fix is high effort (4 years). Scanned in 2026 with 2033 as the quantum year: 25 + 4 = 29 years, against 7 years left. The margin is 22 years, so it's Act now: trim what the integration sends. If you mark that integration as carrying only short-lived data, the same finding drops to Monitor.

Best-practice defaults for standard objects

Used only when the object exists in the scanned org. Objects that exist in every org whether used or not (such as PaymentMethod) are left out, because their presence says nothing about your data.

ObjectAssumed dataWhy
ContactPersonal datapeople’s names and contact details
LeadPersonal dataprospects’ names and contact details
IndividualPersonal dataconsent and privacy preferences
ContactPointEmailPersonal dataemail addresses
ContactPointPhonePersonal dataphone numbers
ContactPointAddressPersonal datapostal addresses
CasePersonal datafree-text customer conversations
AccountConfidential businesscustomer relationships (personal data with person accounts)
OpportunityConfidential businesspipeline and pricing
ContractConfidential businesscontract terms
OrderConfidential businessorder history
QuoteConfidential businesspricing
IdentityDocumentLong-lived regulatedidentity documents
FinancialAccountLong-lived regulatedfinancial accounts
FinServ__FinancialAccount__cLong-lived regulatedfinancial accounts
FinServ__Card__cLong-lived regulatedcard data
HealthConditionLong-lived regulatedhealth records
ClinicalEncounterLong-lived regulatedhealth records
PatientMedicalProcedureLong-lived regulatedhealth records
MedicationStatementLong-lived regulatedhealth records
CarePlanLong-lived regulatedhealth records
HealthCloudGA__EhrPatient__cLong-lived regulatedhealth records

What this does not do