Every business keeps something it would rather not lose control of: the payroll register, the client list, the correspondence that reads badly when quoted back under oath. Constitution Computing sets the defense of those things down in writing as six Articles, each one stating what is covered, what it costs by the unit, and where the cover ends.
A security vendor asks for standing inside everything you own. Here is what that standing is limited by, stated before you buy rather than discovered afterwards.
Each Article names its scope and, in the same breath, names what falls outside it. A page that lists only capabilities is a sales document. A page that also lists the boundary is a specification, and it is the only kind we publish.
Where an Article stops, we say which other Article picks the work up, or we say that nobody does. Both answers are useful the week something goes wrong.
Rates are printed on this page beside a unit you can count without assistance: a machine, a mailbox, a tenant, a company file. Add a line and it shows on the next invoice. Drop one and it leaves by the same door.
Nothing here renews for a year because you missed a notice window. Consent that has to be withdrawn in writing sixty days early is not really consent.
Detections are reviewed by an analyst before they become your problem or your interruption. Software decides in milliseconds; a person decides whether the decision was right, and carries the escalation if it was not.
The failure we design against is the console nobody has opened since the week it went in. A finding nobody reads protects nobody.
Three questions, plainly put. Answer each one truthfully about your own operation and the right subscription assembles itself, including the lines you are entitled to skip.
What is permitted to run, and who said so?
An endpoint is a list of programs that are allowed to execute, whether or not anyone has ever written that list down. Allowlisting writes it down and enforces it. Patching narrows the list of exploitable things on it. Web filtering and mail defense cut the supply line that gets new items onto it in the first place.
Who is watching at three in the morning?
Prevention fails eventually, usually against credentials that were legitimately issued. What matters after that is the interval between the first unusual action and somebody competent looking at it. Our answer is an agent that can isolate a machine on its own judgment and a staffed desk that reviews the isolation, at the hour it happens rather than on Monday.
If both of those fail, what do you still hold?
Ransomware crews go looking for reachable backups first, since an organization able to restore feels no pressure to negotiate. Ours are encrypted, kept beyond the tenant and the credential set they cover, and exercised on a schedule that ends in a dated report. Until a restore has actually been carried out, what you hold is a belief rather than a control.
Quantity is a count you already keep: endpoints, mailboxes, servers, licensed users, tenants. Take as many lines as the estate calls for, and checkout folds the lot into one subscription.
Rates published here · priced per unit · payable in advance
An agent on the machine that can act without waiting for a person, and a staffed desk that reviews what it did. Six lines, separated by how far the evidence reaches and by who is permitted to pull the trigger.
Antivirus asks whether a program looks harmful. Allowlisting asks whether it was ever approved, and refuses everything else by default. One line, one decision, applied to every executable on the endpoint.
Most intrusions arrive as ordinary mail from a name the reader recognizes. Two lines: one filters and remediates the message, the other rehearses the people who open it.
Patch level, disk health, web egress, Apple configuration, and the phones nobody counts as computers. Four lines that turn an estate you assume you know into an inventory you can actually read.
Before you can defend sensitive records you have to find them, and they are never only where the policy says. Two lines: one measures the exposure, the other closes it.
The copy held somewhere your attacker has no standing to reach. Nine lines covering machines, servers, virtual estates, the four cloud platforms your work actually lives in, and proof that a restore succeeds.
Enrollment is short on purpose, and it ends in a service nobody has to remember to check. Any control that depends on being remembered has a hole in it by design.
Pick your lines and their quantities, then complete checkout. Payment runs through Stripe: the card goes straight there, and neither this page nor our systems ever hold it.
We stand up your tenancies and email the enrollment package: agent installers for the machine lines, and authorization links for the cloud platforms. Usually the same business day.
Agents report in, jobs run to their schedules, and findings arrive at the desk rather than a dashboard. The portal keeps your schedule, the installer set, and every case running between us.
Heads up: card statements show FORTIFY 24X7 - Constitution Computing is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.