Security: Cybersecurity & InfoSec Articles | ilia.ae
Russia regulations for tech companies: 152-FZ, 187-FZ, 63-FZ, e-documents and the Bank of Russia Security
Russia regulations for tech companies: 152-FZ, critical infrastructure, e-documents, signatures and the Bank of Russia
This is the fourth article in a series on what a technology company faces in different regions. The earlier ones covered the UAE, the Gulf and Egypt and the CIS. Russia regulations get an article of their
CIS regulations for tech companies: Kazakhstan, Uzbekistan, Kyrgyzstan, Belarus, Armenia and Azerbaijan Security
CIS regulations for tech companies: Kazakhstan, Uzbekistan, Kyrgyzstan, Belarus, Armenia and Azerbaijan
This is the third article in a series on what a technology company faces in different regions. The first two covered the UAE and the Gulf and Egypt; this one covers CIS regulations: Kazakhstan, Uzbekistan
Gulf regulations for tech companies: Saudi Arabia, Qatar, Bahrain, Oman, Kuwait and Egypt Security
Gulf regulations for tech companies: Saudi Arabia, Qatar, Bahrain, Oman, Kuwait and Egypt
This is the second article in a series on what a technology company faces in different regions. The first covered the UAE; this one covers Gulf regulations and Egypt: Saudi Arabia, Qatar, Bahrain, Oman, Kuwait and Egypt.
UAE regulations for tech companies: federal, Dubai, DIFC and ADGM Security
UAE regulations for tech companies: data, cybersecurity, e-invoicing and e-signatures
I work from Dubai Airport Free Zone, and in the article on fintech I wrote that the region’s rules add up to “constraints that must shape your cloud-region choice before the first line of code, not after.”
An AI agent's boundary: a robot at a panel where only read is on, write is locked and delete is chained Digital
An AI agent with access to production: the boundary lives in code, not in the prompt
I run AI agents with access to my site and infrastructure: they edit and publish articles, clean up the media library, rebuild reports, and log into servers over SSH. This article is about where the boundary
An OpenBao secrets store: a safe with five keyholes, three hardware keys, a sealed paper share and a padlock, an unopened HSM box on a shelf Security
OpenBao and Shamir shares: how I built a secrets store
This is an article about a secrets store I have built and not yet opened. The deployment pipeline is finished, all five share holders have passed the rehearsal, and the initialisation ceremony, after which
A reverse proxy on your own hardware: two gatehouses, caddy and traefik, and who owns the certificates Digital
Reverse proxy on your own hardware: Caddy, Traefik and the price of defaults
What belongs in front of your services is not the fastest reverse proxy but the one whose defaults you are willing to live with for three years. Defaults, not feature tables, decide what happens to you
A Kubernetes cluster on bare metal: three nodes behind a default deny fence and four doors that bypass admission control Digital
Kubernetes cluster on your own hardware: building it and locking it down
Most companies that ask me about Kubernetes do not need a Kubernetes cluster. That is the first thing I say on the call, and half of those conversations end there, to everyone’
Go Guard: the command travels from the device, not to it: the agent polls the command server Digital
Go Guard: How a Self-Built MDM Platform Works
An employee left a laptop in a taxi on Friday evening. The machine goes into lockdown from the panel, which also shows whether disk encryption is on and where the device was last seen, and the decision
SIEM on an open core: Wazuh and OpenSearch plus a custom correlation layer Security
A SIEM on an Open Core: What Is Ours and What Is Not
When a contractor calls a SIEM “our own product”, it is worth asking what exactly is theirs. In our case the answer is this: ours is the layer on top of an open core, not a rewritten engine.
A self-hosted MDM inside the customer perimeter instead of a vendor cloud Digital
A Self-Hosted MDM Instead of Intune and Jamf: When It Pays Off
Device fleets are usually managed with Intune, Jamf or Hexnode, and in most cases that is the right call. We built a self-hosted MDM not because the ready-made ones are bad, but because for our profile
Hidden OS on UEFI: two independent encrypted Windows perimeters on one disk Security
Hidden OS on UEFI: the Windows Perimeter Nobody Can See
A hidden OS is a second encrypted Windows perimeter on the same disk of an ordinary laptop, whose existence cannot be established from the running system, from the bootloader, or from a sector-by-sector disk image.