Inspiration
Regional SMEs are targeted by scams and audits but lack security staff. We wanted a local, lightweight tool that turns messy control responses into clear, audit-ready outcomes using the node we built for CYBERPULSE AI.
What it does
It evaluates control responses inside n8n and classifies them as Compliant, or Non-Compliant. It adds explain and recommend notes, scores confidence, and maps actions to PCI DSS, ISO 27001, NIST CSF, SOC 2, Essential Eight, and GDPR. It outputs audit fields such as evidence_count, mapped_count, and summaries and recommendations for reproducible reporting.
How we built it
We used the CyberPulse Compliance custom node in a simple n8n workflow. The node applies rule logic and a crosswalk.json to map responses to frameworks. We kept everything local and reproducible with a Windows build guide and a short install checklist.
Challenges we ran into
Keeping results consistent across laptops and desktops was harder than expected. We solved environment drift, npm packaging issues, and version visibility by tightening paths, scripts, and verification steps.
Accomplishments that we're proud of
A node that produces clear status, score, and confidence with framework mapping. A minimal workflow that judges can run in minutes and export as clean logs. Documentation that makes the install, test, and update path straightforward.
What we learned
Small, focused automation beats big platforms for regional teams. Evidence-aware scoring and explicit mappings reduce debate during audits. Versioned rules in an external crosswalk let us update logic without rebuilds.
What's next for CyberPulse Compliance Co-Pilot (Outback Edition)
Add preset packs for common SME stacks and Australian guidance alignment. Publish more case examples with before and after metrics. Expand exports to dashboard tiles and one-click audit bundles.
Log in or sign up for Devpost to join the conversation.