How we work
Editorial Policy
We publish guidance about certification fees, licensing costs and security requirements. People budget against it. This page sets out who writes it, how it is checked, how often it is reviewed, and what happens when we get something wrong.
Editorial lead: Chris Dunham, Founder · Last reviewed
Who writes this
Everything published here is written by the AIS Technology team, working from the jobs we actually do. Editorial responsibility sits with Chris Dunham, Founder.
Chris Dunham began his career in network security, going on to secure the digital infrastructure of major financial institutions and government organisations including the UK Home Office, before founding AIS Technology.
Where a piece covers something outside our own experience, we say where the information came from and link to the source so you can read it yourself.
How we research a piece
We go to the body that owns the subject first. Certification requirements and fees come from IASME. Licensing and product detail comes from Microsoft. Regulation comes from the regulator or from legislation, not from someone else's summary of it.
Where we quote a figure, we quote the published figure and date it. Where a number comes from a study rather than a primary source, we say so rather than presenting an estimate as a fact.
We do not publish a number we cannot point at a source for.
Review before publication
Every article is read by an engineer who works in that area before it goes out. They are checking one thing: would this hold up in front of a client.
Anything that touches cost, compliance or a security control gets a second read against the current published requirement, because those are the pieces where being out of date does real damage.
Keeping it current
Standards move. Cyber Essentials changes its question set. Microsoft changes its licensing. A guide that was right in January can be wrong by April.
So we review the guides on a schedule and after any change we know about. Each article carries the date it was published and the date it was last updated, and those dates are real. We do not bump a date to look fresh.
When an update changes the substance of a piece rather than tidying it, we say what changed.
Corrections
If we get something wrong, we fix it and we leave a note saying what was wrong. We do not quietly edit an error out.
If you spot one, tell us at info@ais.london. We would rather hear it from you than leave it up.
What we will not do
We do not take payment to feature a product, and we have no affiliate or referral arrangements with the vendors we write about. Where we name a product, it is because we use it or deploy it.
We name our partner relationships openly. We are a Microsoft Silver Partner, and we hold partnerships across Dell and Cisco. That shapes what we are good at; it does not buy a mention.
We do not publish content generated wholesale by a language model and passed off as our own. Drafting tools may help with structure. The substance, the numbers and the judgement come from people who do this work.
We do not scare people into buying. Security marketing has a bad habit of it, and it makes for worse decisions.
Reviews and testimonials
The reviews shown on this site are real and unedited beyond formatting. Our Trustpilot rating is 4.7 out of 5 from 44 reviews, and the full record, good and bad, is on Trustpilot rather than curated here.
We do not offer anything in exchange for a review.
What this content is not
It is general information, not advice about your business. It is not legal, financial or regulatory advice.
Read it, use it to ask better questions, then take proper advice before you act. Our Terms of Service set this out in full.
See also our Terms of Service and Privacy Policy.
Spotted Something We Got Wrong?
Tell us and we will fix it, with a note saying what changed. We would rather hear it from you than leave an error up.
AIS Technology, Woodland Place, Hurricane Way, Wickford, SS11 8YB