Secure your 1Password surface
Vault membership, credential age, and secrets shared far beyond the people who need them. We don’t connect to 1Password to collect evidence for its own sake — we connect to secure it, and the compliance artefacts follow from that work.
Book a Demo[01] What This Surface Exposes
Where 1Password goes wrong
1Password goes wrong through vault sharing: a credential reaches a group far larger than the handful of people who need it.
- Vaults shared with groups far larger than the credential's audience
- Credentials never rotated, including ones for systems that have since changed hands
- Items flagged as weak, reused, or appearing in known breach corpora
- Guest accounts and external shares retained past their purpose
- Recovery and break-glass procedures untested or held by too few people
[02] What We Secure
What we watch, catch and fix on 1Password
On 1Password we reconcile vault membership against role so credential access follows the same review as everything else.
- Vault membership reconciled against role so credential access follows the access review
- Credential age tracked per item, with rotation prioritised by what the credential protects
- Breach and reuse findings triaged against system criticality rather than reported as a raw score
- External sharing monitored for credentials leaving the organisation
- Break-glass custody reviewed as an availability risk, not just a security one
[03] Where It Lands
Where 1Password lands in your registers
Directory data drives your access reviews directly: reviewers see live entitlements rather than a spreadsheet exported three weeks ago, and leaver revocation is verified against the systems themselves. The asset register records each identity provider as a critical dependency, and the risk register carries the concentration risk that comes with it — because if this tier fails, everything behind it fails with it.
[04] How We Engage
On 1Password specifically
On 1Password, we remove stale vault access and external shares, and drive rotation of exposed credentials. Restructuring the vault model to match your team topology we plan with you.
Platform licence
Everything you need to find and fix it yourself, with no ceiling on the depth of the answer.
- Every connected tool monitored for misconfiguration and drift, with findings mapped to the assets and risks they affect
- Remediation guidance that tells you what is wrong and exactly how to fix it — however deep or awkward the issue is. We are engineers running a security company, so the answer is the real one, not a link to vendor documentation
- Assets, access reviews, and risk register populated from the tools themselves rather than from spreadsheets
- Unlimited integrations and unlimited users, with anything missing built within two weeks
Managed service
Every tool you connect through Konfirmity comes under our care, with our team doing the work.
- Continuous misconfiguration and drift monitoring across every connected tool, watched by our analysts rather than by a dashboard waiting for you
- Incident response led by us, with containment coordinated with your team
- Remediation performed directly wherever you have granted us the authority to act — and where we cannot act, we project-manage the fix to completion rather than handing you a ticket
- Decision support on the tools themselves: where something is failing you on capability or costing more than it returns, we will tell you, and help you replace it
[05] 1Password FAQs
Can Konfirmity see our stored passwords?
No. Konfirmity reads vault and item metadata through the Events API and admin endpoints — who has access, when an item was last changed, whether it appears in a breach corpus. Secret values are never retrieved, and the integration has no capability to do so.
How do you prioritise credential rotation?
By what the credential protects, not by an abstract strength score. A weak password on an unused internal tool matters less than a strong one shared with fifteen people who no longer need it. We rank rotation against asset criticality from your register.
Okta
Microsoft Entra ID
Google Workspace
Auth0
JumpCloud