Security event aggregation
Read-only ingestion of authorised findings from GuardDuty, Security Hub and CloudWatch into one normalised stream.
Defensive monitoring · read-only · analyst-reviewed
SecureMesh is a proposed platform that consolidates authorised security findings, correlates them into incidents and drafts evidence-based summaries — so analysts spend their time on what matters, and decide every response.
Sample day from the prototype, synthetic data.
// from noise to signal
Findings from different tools describe the same event. SecureMesh groups them by shared resource, identity and time, removes duplicates and ranks what is left — each step shown, nothing hidden.
iam-user/deploy-botiam-user/deploy-bots3/customer-exportss3/customer-exportsstaging-web-01staging-web-01staging-web-01build-runner-07build-runner-07root-accountroot-accounts3/marketing-assetsprod-db-clusterprod-db-clusterprod-payments-apistaging-web-01// capabilities
Read-only ingestion of authorised findings from GuardDuty, Security Hub and CloudWatch into one normalised stream.
Flags behaviour that departs from each identity’s and asset’s baseline — new networks, sudden request spikes, unusual logins.
Correlates related findings and ranks incidents P1–P4 from severity, asset criticality, corroboration and confidence.
A plain-language timeline built only from the findings, with sources — drafted for an analyst to review, never sent on its own.
Open incidents by priority, source and asset; time to acknowledge; what was marked benign and why.
Analysts open cases, add notes, move them through investigating, contained and closed, with a closing summary.
Analyst, lead, CISO and auditor roles; every decision logged with who and why; exportable reports.
AI-assisted alert triage that combines event context with analyst-reviewed incident summaries. The machine does the gathering; people do the judging.
// transparent priority
No black box. Every incident shows exactly why it ranks where it does. Move the inputs and watch the priority change — it’s the same formula the triage console uses.
score = severity/10 × criticality/3
× (1 + 0.25 × (signals − 1))
× confidenceP1 ≥ 60 · P2 ≥ 35 · P3 ≥ 15 · otherwise P4. Thresholds are configurable per team.
// built for
One queue across accounts and tools, with priorities leadership can follow.
Small security teams covering fast-changing cloud estates without drowning in alerts.
Many customer environments, consistent triage and audit-ready reporting for each.
Decision-makers CISOs · security analysts · IT infrastructure managers
// business model
Subscriptions based on the number of monitored environments, with 5 GB/day of findings and logs included per environment and usage beyond that billed by volume. Illustrative pricing for a proposed product.
$750/ month · $720 for environments + $30 for 5 GB/day over the included volume
Request a demo// planned AWS infrastructure
SecureMesh is a proposed defensive monitoring platform for enterprise IT teams, SaaS companies and managed security providers. It works on a continuous stream of findings from authorised sources, which must be consolidated, explained and kept as protected records. Designing on AWS lets it read findings where they already live, process them as they arrive and store them with strict access controls.
Amazon GuardDutyAWS Security Hub
Threat detection findings and aggregated security findings are read from the customer’s authorised accounts, read-only.
Amazon CloudWatch
Operational alarms and logs add context, such as a deployment or an outage at the same time.
AWS Lambda
Findings are normalised, de-duplicated and correlated into incidents by resource, identity and time.
Amazon Bedrock
Evidence summaries are drafted from the correlated findings for analysts to review.
Amazon S3
Findings, incidents, case notes and audit reports are stored encrypted with restricted access.
// across every stage
SecureMesh is a proposed defensive cybersecurity monitoring platform for enterprise technology teams, SaaS businesses and managed security service providers. The planned application will consolidate authorised security findings, prioritise alerts and generate evidence-based investigation summaries for analyst review. We plan to use Amazon GuardDuty, AWS Security Hub and Amazon CloudWatch as sources of security and operational findings, alongside Amazon Bedrock for summarisation. Amazon S3 and AWS Lambda will support protected record storage and processing. Security professionals will evaluate findings and determine incident response actions.
Planned, not yet deployed. This website and the triage console run in your browser on synthetic data.
// founder
David founded SecureMesh after seeing security teams lose real incidents in a flood of duplicate, unexplained alerts. David leads product, customers and every pilot, with a focus on read-only, analyst-first tooling.
// progress & demos
SecureMesh is a proposed product in its building stage. A demo walks through the review workflow: findings in, incidents ranked, a summary drafted and an analyst deciding. The MVP covers read-only ingestion of authorised findings, alert categorisation, evidence summaries and manually managed incident cases.
By David Emeka, to give security teams fewer, better-explained alerts.
Read-only ingestion, correlation into incidents, transparent priority scores, analyst-reviewed summaries.
Findings, incidents, evidence summaries, case management and audit export on synthetic data.
Finding sources, aggregation, summarisation, storage and processing designed.
Read-only ingestion of authorised findings for one environment, with analysts deciding every response.
// faq
No. It is read-only and never blocks, quarantines or changes anything. Analysts review incidents and decide every response in their own tools.
Only findings and logs from sources you explicitly authorise, such as GuardDuty, Security Hub and CloudWatch in your own AWS accounts.
In the planned product, Amazon Bedrock would draft summaries strictly from the correlated findings. They are labelled as drafts until an analyst reviews them. The prototype uses a deterministic template.
Not yet. It is a proposed product; the triage console is a prototype running in your browser on synthetic findings.
// contact
Questions about the product, integrations, data handling or partnerships. Messages go directly to the founder.