Macula Mesh Use Build Macula for… Docs Contact

Macula · sectors · All Macula for… pages

With Macula, your servers tell other operators which addresses attack them, as signed messages. Your server sends three things per attacker: the address, the number of tries and the user names it tried. The rest of the log never leaves the machine. A witness tests a security claim every hour and signs the result. Anyone can check that no hour is missing and none was changed afterwards. We are looking for security teams, hosting operators and researchers to build it with.

Without Macula: security tools upload your logs to their vendor's cloud

Every server on the internet gets login attempts from strangers, and the same addresses hit many servers. Most security products are SaaS: a cloud SIEM or EDR uploads your logs to the vendor's cloud, and what the vendor learns from all its customers is shared on its terms, if at all. Public blocklists such as AbuseIPDB are a single database run by a single operator.

logs copied out

A cloud SIEM or EDR keeps a copy of your logs

A cloud SIEM or EDR reads your logs on its vendor's servers. Those logs name your machines, your users and your accounts, and once uploaded they are stored under the vendor's control, not yours.

one breach hits all

A cloud security service holds every customer's logs in one place

A service that holds every customer's logs is worth attacking for that alone. When it is breached, goes down or changes its terms, every customer is hit at once.

claims unchecked

An annual audit checks a security claim once a year, if at all

"We only use post-quantum key exchange." "We run signed releases." Claims like these sit in a vendor document or an annual audit report. Between audits, all you have is the vendor's word.

With Macula: signed sightings instead of logs, signed checks instead of promises

Each server runs a Macula node that dials out to the Macula Mesh, a network of stations that link up to form the mesh, keep its phonebook (a Kademlia DHT: which node offers what, and where to reach it), and relay messages between authorized members. One mesh carries many Macula Realms. Each realm is an identity space on the mesh with its own key: its operator admits anything that can be given an identity, such as people, organisations, services, machines and devices, gives each a certificate signed with that key, and can revoke it. Macula runs the community realm; a company or sector body can run its own under a Macula licence. Over the mesh, servers send each other signed reports of attacks instead of logs, and a checker publishes signed results instead of a promise.

Every node connects outward. The stations relay sightings without keeping them, and besides the mesh's phonebook they hold only a witness's latest record. A sighting carries only what the warden saw (the address, how many tries, the names it tried), and a witnessed claim carries its verdict, its signature and the hash of the record before it.

The two things it does

shared sightings

Each server reports the addresses that attack it

  • A warden on each server reads that server's own login log. When one address fails to log in 5 times in 5 minutes, it publishes a signed sighting: the address, the count and the user names tried.
  • The rest of the log never leaves the machine. By default the warden only watches; it does not block anyone. An operator can opt into a tarpit that accepts connections on decoy ports and holds them open, publishing how long each was held. It never initiates a connection to the attacker.
  • A sentinel takes sightings only from the wardens it is told to trust, by the signature the mesh checked, and keeps each one as evidence in its own log, in order, on a machine other than the attacked servers.
  • When a second server sees the same address, the sentinel says so, and how long the shared view knew that address before this server met it.

witnessed claims

Each security claim is checked every hour and the result signed

  • A witness probes the running system for a declared claim, such as "this station accepts only post-quantum key exchange" or "this station runs a signed public release".
  • Every hour it judges the claim holding, broken or unknown, signs that verdict, and links it to the verdict before by its SHA-256 hash.
  • A keeper copies every record into a public archive and logs when it first saw each one.
  • Anyone can re-check the whole chain offline with the open-source fovea tool and the published key of the witness's realm. A missing hour, a late record or a second history shows.

Report the addresses that attack you; your logs stay on your machines. A witness tests the claim every hour and signs the result. Anyone can check that no hour is missing and none was changed afterwards.

What Macula promises

no log leaves

Your logs stay on your server

Your server sends three things per attacker: the address, the number of tries and the user names it tried. The rest of the log never leaves the machine.

signed facts

A message cannot fake its sender

Every sighting and every record is signed by the machine that published it, and the signature is checked before delivery. A sentinel goes by the signature, never by what a message says about its own sender.

you choose

You choose whose reports you accept

A sentinel accepts sightings only from the wardens you list. Nobody shares with you, or reads yours, unless you set it up.

gaps show

Lost messages show up as gaps

Sentinel facts are numbered and sent with a heartbeat, and witness records are chained, so a lost message or a missing hour shows as a gap, not as a quiet day.

evidence kept

Kept evidence is append-only

Each sighting is stored as an event that is added and never edited, and each witness record is signed and linked to the one before.

no cloud

No vendor cloud holds your data

The stations pass messages on and keep no logs of yours. Besides the mesh's phonebook, a station holds one more thing: each witness's latest record. You run your own sentinel, it stores your evidence, and you list whose reports it accepts. Your realm's admin only decides who and what is admitted.

See it run

Twelve public servers of the Macula fleet each run a warden, and one sentinel listens to them. A witness checks two claims about six stations of the fleet every hour. These pages are drawn from their facts:

live

The Vigil

A live map of where login attempts come from and which servers they hit, with each address that a second server has seen.

history

The record

Every sighting the sentinel kept, as a table you can group: by server, country, network, user name or hour, over the last hour up to thirty days. Lost facts are marked, not hidden.

witness

Fovea

The witness at work: who probes, signs, keeps and re-checks, and every hourly verdict in its chain, gaps included.

The archive of witness records is public at github.com/macula-io/mcl-fovea-records, and the tool that checks it at github.com/macula-io/macula-fovea. Locations of addresses come from IP Geolocation by DB-IP, CC BY 4.0.

What the sightings make possible

The record is already more than a map. The same signed sightings can become a campaign brief, an abuse report a network can verify, or a model a member runs at home.

campaigns

A sighting becomes a campaign

When a second warden sees the same address, the sentinel already names a campaign. The record can carry the addresses, the networks, the user names and the timing as one brief, with every claim linked to the signed facts behind it.

abuse reports

Evidence an ISP can check

The sentinel keeps each sighting in order, off the attacked box. A report drawn from that store carries the signed facts and a chain of custody, so the network that owns the address can verify it instead of trusting a screenshot.

models

A model trained on the commons

The same facts can train a small model that scores an attempt or names a campaign. A member runs it on its own machine: the model travels, the evidence does not.

Where it fits

Teams that defend machines and want to share attack data while their logs stay on their machines, and anyone who wants a security claim tested every hour instead of asserted. With partners we want to build the rest: wardens on their own servers, sensors for more than login attempts, decoys that keep an attacker busy and let it believe it got in, and their own claims checked by a witness.

Security operations teamsManaged security providersHosting operatorsThreat-sharing groupsAuditors and assurance researchers

Build it with us

Partners bring the machines, the attacks they see and the claims they want tested; we bring the station software, seed stations, the warden, the sentinel and the witness, and each partner gets a realm of its own under a Macula licence or a place in the community realm. We are looking for partners in three roles.

share sightings

Security teams and providers

You watch machines for yourself or for clients. Run wardens on them and a sentinel of your own, and choose whose sightings you hear and who hears yours.

many servers

Hosting operators

Your machines get login attempts from strangers every day. Turn those attempts into shared evidence without any log leaving the machines.

test a claim

Auditors and researchers

You check whether security claims hold. Declare a claim with us, have a witness check it every hour, and let anyone re-check the record.

In one sentence

Tell other operators who attacks you and hear who attacks them; your logs stay on your machines.for security teams

Signed sightings from each server to the sentinels that trust it, and signed, chained verdicts anyone can re-check offline.for architects

Shared attack data and security claims anyone can re-check, with no vendor holding the data; each realm's admin decides who and what is admitted, and nothing else.for funders and policy makers