Secure your Heroku surface
Config vars holding plaintext secrets, unmaintained buildpacks, and collaborator sprawl across apps. We don’t connect to Heroku 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 Heroku goes wrong
Heroku goes wrong through config vars: they hold your production secrets in plaintext and every collaborator on the app can read them.
- Config vars carrying database URLs, API keys, and signing secrets in plaintext
- Apps running on deprecated stacks or buildpacks no longer receiving security updates
- Collaborators retained on apps long after they stopped needing them
- Add-ons with their own data stores and their own access model, outside your main review
- Team members without two-factor authentication on an account that can deploy production
[02] What We Secure
What we watch, catch and fix on Heroku
On Heroku we treat config vars as a secret store with rotation tracked per value, and reconcile collaborators against your HR record.
- Config var inventory treated as a secret store, with rotation tracked per value
- Stack and buildpack currency monitored against end-of-life dates
- Collaborator access reconciled against your HR system so leavers actually lose access
- Add-on inventory captured as assets, because that is where regulated data often ends up unnoticed
- Deploy activity tied to change approvals
[03] Where It Lands
Where Heroku lands in your registers
Every cloud resource we discover becomes an entry in your asset register with an owner, a criticality rating, and its data classification. Access reviews cover the IAM principals attached to it, and the risk register carries the mapping between the asset and the risks it actually carries — so a public bucket is a named risk against a named asset, not a line item in a scan report.
[04] How We Engage
On Heroku specifically
On Heroku, we remove stale collaborators and drive secret rotation through your pipeline. Stack upgrades and migration off end-of-life buildpacks we plan and run with your team.
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] Heroku FAQs
How do you handle Heroku config vars containing secrets?
We inventory them as credentials rather than as configuration, tracking what each one grants access to and when it was last rotated. We never store the values themselves. Where a config var is readable by collaborators who should not have it, that is reported as an access finding.
Do you track Heroku add-ons?
Yes. Add-ons are where regulated data most often ends up unnoticed, because each one is a separate service with its own data store and its own access model. Konfirmity captures them as assets so they appear in your register rather than sitting outside it.
Amazon Web Services
Google Cloud Platform
Microsoft Azure
Kubernetes
Terraform