Occlude
Book a call

Blog

The security model stated plainly, the alternatives teams use today, and the decisions behind the product. Each post names its sources.

  1. The memory-dump problem, stated plainly

    The compiler reads the code a contractor cannot, so that code is in memory. Who can read that memory, what stops them, and what we do not claim.

  2. Four states, not two

    Most access control has two answers. Occlude has four, because "denied" tells someone the file exists, and credentials need a different answer.

  3. Perforce controls what syncs. Occlude controls what runs.

    Perforce has kept files from contractors for decades, and its manual says what it costs: the build. Why hiding files at runtime does not.

  4. The five things teams do today

    Five ways teams hand code to a contractor or an agent today: what each gets right, where each stops, and which one we lose to most.

RSS feed