Focused IoT audit for the path under pressure
Combotto audits one gateway, MQTT, ingest, identity, or observability path at a time. You get a leadership-ready summary, evidence-backed findings, and a prioritized backlog your team can use to fix internally, move into a focused sprint, or pause with clarity.
Proof-led engagement path
Audit baseline exposes the findings. The hardening rerun verifies the fixes. Retainer review keeps later drift visible.
Most intro calls only need 20 minutes to confirm the path, the decision deadline, and whether the audit should start there.
Field setup behind the proof
This Raspberry Pi 5 gateway, power bank, and three STM32 devices are the same field setup behind the audit baseline, hardening rerun, and delta review shown below.
Live proof
This is the decision story the engagement is meant to produce: expose the weak path, prove the fix held on the same surface, then keep later releases anchored to that stronger baseline.
1. Audit
One run turned a vague gateway concern into a concrete finding set on the live telemetry path.
Baseline summary before hardening
2. Sprint
The same path was rerun after hardening, so the close-out is evidence instead of intent.
Follow-up summary after hardening
3. Retainer
The hardened state became the reference point for later release or monthly checks.
Delta report: before vs after
Decision unlocked
Start with one live path, make the exposure legible, verify the fix on that same surface, and carry the stronger state forward as the next baseline.
Audit → Sprint → Retainer
Most teams should stop after the audit unless the findings justify a narrower follow-on. Each stage uses the same path, the same evidence logic, and a tighter next question so it stays clear where the work starts, what the team gets, and when continuing is actually worth it.
Baseline the real path first
Harden only what the audit proved matters
Keep only the drift checks worth repeating
Starts with
One selected gateway, MQTT, ingest, identity, or observability path already under pressure.
You leave with
Leadership summary, evidence-backed findings, prioritized backlog, and verification logic for the exposed path.
What it settles
Whether the team should fix internally, continue into a focused sprint, or pause with a clear view of the exposure.
Starts with
Only the backlog rows with enough risk, customer pressure, or operational cost to justify follow-on work.
You leave with
Focused hardening changes on those rows, rerun evidence on the same path, and before/after proof that shows what actually improved.
What it settles
Whether the path is now strong enough to ship, pass review, or keep operating without carrying the same exposed rows forward.
Starts with
Only the latest validated path and the handful of checks most likely to drift between releases.
You leave with
Delta review, regression signal, and refreshed priorities tied to the last validated run instead of a new broad discovery cycle.
What it settles
Whether posture is holding between releases, what changed since the last baseline, and when another focused sprint is actually warranted.
Is this the right starting point?
This is for teams that need fast evidence on the gateway, MQTT, or edge-to-cloud path carrying the pressure. It is not another broad discovery cycle. It is a focused audit that shows what is solid, where confidence breaks, and what the smartest next move is.
If one of these situations is already true, the audit is usually the right first engagement.
Review pressure
Customer, procurement, or internal review pressure is arriving faster than the team can defend the current gateway, MQTT, or ingest posture with evidence.
Audit makes clear: What is solid, what is exposed, and what needs to change before customer, procurement, or internal review becomes a blocker.
Decision unlocked: Leadership gets a defendable continue, pause, or fix-first position before the review becomes the thing steering the roadmap.
Telemetry distrust
Duplicate events, weak observability, unclear retry behavior, or missing data are eroding confidence across device, gateway, broker, and ingest.
Audit makes clear: Exactly where trust breaks across the live path, so engineering gets a real failure picture instead of another theory-heavy workshop.
Decision unlocked: The team can decide whether to instrument, harden transport, change buffering behavior, or stop trusting the current signal until the path is fixed.
Launch or scale pressure
Earlier transport, identity, buffering, or operational choices that were acceptable during delivery are now being tested by launch, customers, or fleet growth.
Audit makes clear: Which decisions are still safe to carry forward and which ones now need hardening so the team can act on the highest-value fixes first.
Decision unlocked: Engineering and leadership can separate what is safe to ship from what needs a focused hardening sprint before launch or fleet growth raises the cost.
Scope guardrails
These boundaries reduce ambiguity without pushing you into a bigger engagement than the evidence supports.
Selected scope
The first audit usually centers on one gateway, MQTT, ingest, identity, or observability path that is already driving the decision.
Specialist lens
This first pass is a system-level audit built to expose architectural, operational, and telemetry risk fast. If the next question is dedicated penetration testing or managed monitoring, that can be scoped after the baseline instead of before it.
Audit-first motion
The audit is the first engagement. Follow-on work only happens if the findings justify a narrower hardening sprint or a recurring review rhythm.
Next step
Use the first note to share the path, the pressure around it, and the decision that needs support. The goal is to get quickly to the right starting scope, any missing context, and whether a short scoping call would be useful.
What to send
Share the gateway, broker, ingest, identity, or observability path that is carrying the risk, plus the launch, review, incident, or reliability pressure forcing the decision.
What the reply covers
It should make it clearer whether this is the right path to audit first, what the initial slice should include, and whether a short call would help.
Typical next step
If the fit is clear, the next step is usually a short call to confirm path, access, and the evidence chain that needs to be reviewed first.
Send the selected scope, what is creating pressure now, and any launch, review, or incident deadline. You’ll get a direct reply focused on the recommended starting scope and next step.
Or contact me directly: +45 22 39 34 91 or tb@combotto.io.
IoT audit FAQ
Send the selected path, what is creating pressure now, and any launch, review, or incident deadline. If you already have diagrams, logs, or screenshots that show the path, include them.
Sometimes, but only the smallest access needed to inspect the live evidence chain credibly. If the right answer is a narrower environment, exported artifacts, or a guided walk-through, that is what the first scope should use.
Yes. The audit is meant to stand on its own with findings, backlog, and a clear next move. Sprint or retainer work only happens if the evidence says the narrower follow-on is worth it.
Yes, when the pressure is tied to one live product path. The audit can inspect disclosure intake, supported release-line truth, evidence gaps, and whether the next step is a focused sprint or a lighter retainer review. The public /security/ route and/security/advisories/ show the reporting front door and publication home; public advisories, CSAF, and regulator filing still stay out of scope until real cases exist.
Optional proof check
The route above should already make the next step clear. These links are here for teams that want one more proof pass before they send the pressured path.
Flagship proof
Rust gateway hardening case study
See the baseline, hardening rerun, and delta review that anchor the same Audit to Sprint to Retainer story on this page.
Supporting context
Combotto Audit Engine is now pilot-ready: repeatable evidence, deltas, and regression alerts
The Combotto Audit Engine is now ready for pilot projects: canonical reports, run-to-run delta tracking, and alerts for regressions and expiring certificates—built to make Audit → Sprint → Retainer delivery faster and more verifiable.
Technical appendix
The main route already shows the commercial path. This appendix is here for teams that want to see how Combotto keeps the audit baseline, hardening rerun, and recurring review rhythm disciplined without turning the main narrative into tooling detail.
See the exposure clearly
Start with a baseline that makes the weak path legible fast enough to support a real decision.
Verify the fix held
Rerun the same trust path after hardening so the sprint ends with evidence, not intent.
Keep drift visible
Carry the smallest useful evidence bundle into recurring review so posture does not quietly slide backward.
How the evidence changes by stage
The first review needs enough surface area to make the pressured path legible. Later rounds should get tighter, faster, and easier to repeat because the team is validating a smaller set of known risks.
Audit
Establish a credible baseline across the path under pressure.
Sprint
Rerun the exact surfaces that should now be stronger.
Retainer
Keep the smallest recurring bundle that still catches meaningful drift.
Evidence bundles
Start broader when the question is still where the exposure is. Tighten the rerun once the question becomes whether the fix held.
Evidence bundle
A broader first-pass baseline for teams that need the real gateway and ingest risk made clear quickly.
Checks included
Broker transport posture · Broker certificate identity check · Ingest authentication check · Gateway guardrail review
Best when
You need transport, identity, ingest, and gateway controls checked together in one clear starting run.
Business outcome
Gives leadership and engineering a shared baseline to decide whether to stop, fix first, or go deeper.
Follow-through
This baseline becomes the reference point for sprint reruns and later milestone reviews.
Evidence bundle
A tighter rerun bundle for proving the hardening work actually improved the path that mattered.
Checks included
Broker transport posture · Gateway guardrail review · Ingest authentication check
Best when
The highest-value fixes are already in progress and the next decision depends on evidence, not confidence.
Business outcome
Shows whether the hardening held on the same trust path that triggered the audit.
Follow-through
Often becomes the default recurring validation bundle after the first hardening pass.
Evidence bundle
A compact certificate bundle for rollout checks, renewal readiness, and recurring endpoint hygiene.
Checks included
Device certificate hygiene check
Best when
The live question is endpoint identity or expiry risk rather than a broader gateway sweep.
Business outcome
Produces tight certificate proof without the noise of a wider rerun.
Follow-through
Useful for periodic certificate hygiene and renewal-readiness reviews.
Checks included
These checks are shown as optional technical depth for buyers who want to understand how the evidence stays repeatable from baseline through follow-on review.
Check included
Best used when
Audit baseline and fast reruns.
What it shows
Whether the live broker connection is strong enough to support launch, review, or scale confidence.
Why buyers care
A strong first-pass proof point when the question is whether the transport path is fit for launch, review, or scale.
Check included
Best used when
Audit baseline and renewal readiness.
What it shows
Whether the broker identity and renewal posture still support what field systems are expected to trust.
Why buyers care
Useful when certificate drift, enterprise review pressure, or renewal risk is becoming a business issue.
Check included
Best used when
Hardening sprint checkpoints.
What it shows
Whether the gateway changes actually raised the posture on the path that triggered the sprint.
Why buyers care
Keeps the sprint focused on the gateway fixes most likely to improve trust, uptime, and review readiness.
Check included
Best used when
Audit baseline and regression bundle.
What it shows
Whether the ingest edge is really protected on the live path rather than only assumed to be.
Why buyers care
Creates a fast, legible proof point when the question is whether the ingest edge is actually protected.
Check included
Best used when
Rollout validation and recurring hygiene.
What it shows
Whether deployed endpoints still present the certificate posture the fleet depends on.
Why buyers care
Useful as a smaller recurring check when certificate hygiene matters more than a full gateway rerun.