who's writing, and how this pays for itself.

what this is

access creep is an independent publication about one question: what has access in your company, and what can it do? It's written for the people who end up responsible for a company's tools, data and workflows without a security team behind them: heads of IT, operations leads, founders, the one engineer everyone asks.

Each guide takes one mechanism, explains how it works, why nobody catches it, and what to do about it this week. Where it helps, it ends with what the problem means if you have to buy something or defend a budget.

who writes it

I'm Dawid Winiarski. I spent close to ten years in B2B sales, marketing and startups, ran two of those startups as CEO, and then moved into cybersecurity. My day job is in sales, marketing and growth at Securivy, a cybersecurity company in Poland. This publication is mine. I write it on my own time, and it contains no employer material.

how this makes money

Reading is free and will stay free. The money comes from introductions. When someone uses thehelp me choose form, I reply with options that fit. If they pick a product and ask to talk to the vendor, I introduce them. Some vendors pay me a referral fee for that.

• I tell you which options pay me a fee before you choose.
• I recommend options that pay me nothing, including process changes and settings you already have, whenever they fit better.
• When an option is sold by Securivy, I say so.
• Your email address and answers are never passed to a vendor unless you ask for that introduction.
• Guides don't contain paid placements. If that ever changes, the piece will say so at the top.

corrections

Every number in a guide names its source, and sources are listed at the end. If something is wrong or out of date, write to dawid@dawid.xyz and I'll fix it and note the change.