The fact, not the file.
Director Shaifudin Selamat has led close-protection details at APEC and at Singapore-hosted ministerial events. He has done this work in partnership with the host nation's security service, alongside the principal's own travelling staff, across the operational envelope of a multi-day, multi-venue programme. He has done it more than once.
That is the part of this engagement that belongs on a public website. The events are publicly recorded as having taken place. The principals attended in roles that are publicly known. The host service's responsibility for the protective bubble is publicly understood. What sits inside that bubble is properly closed.
The reasons not to write things down.
The specifics of a close-protection assignment — the principal's identity, the venues, the routes, the timing, the team composition, the contingency plans, and any incident or near-incident inside the operation — do not appear on this page, and would not appear on this page even if our client wanted them to. There are three reasons.
- The principal. A close-protection detail exists to keep someone safe. Writing about that detail in detail makes the next detail harder to keep safe. The professional standard is to keep silent.
- The host service. A multilateral event is run by the host nation's security service. They lead. Hawkeye supports. Their operational confidentiality is theirs to maintain; we do not publish material that sits inside it.
- The future brief. Future principals and future hosts decide whether to engage a firm based on whether that firm can be trusted to be discreet. The single best signal we can give a future client is that the last client's details are not searchable on our website.
The work behind two metres.
What we can describe — at the right altitude, without compromising any specific assignment — is the shape of the discipline. A close-protection detail is preceded by a threat assessment, a route survey, an advance team's recce, a venue protocol-check, and a series of contingency-routing rehearsals. It is operated under a structured detail-leader command, with clear escalation to the host service, the principal's chief of staff, and the principal themselves. It is briefed before every leg of the programme and debriefed after every leg. It is rehearsed; it does not improvise.
The two-metre-behind position that the public sees is the visible point of an operation that began, on a typical assignment, several weeks earlier in survey work. The officers selected for ministerial details are senior, drilled, briefed, and on a separate roster from the general operational floor. Director Shaifudin Selamat selects the team for every detail he leads.
This page is not a sales pitch for ministerial work, nor an invitation to discuss specific principals on a website form. Close-protection engagements at this level begin with a director-to-director conversation under appropriate non-disclosure and proceed only when the host service and the principal's own staff agree to the engagement structure. If your brief in front of you is in that category, contact details are on the home page and a director will return the call.
Because it is true, and because it is brief.
Most pages on this site go into operational detail because the work in question is the kind of work that improves with operational detail. A national stadium contract is more credible if you understand the venues. A bank AGM is more credible if you understand the registration screening. A counterfeit-warrant catch is more credible if you can read the SPF letter that followed.
This page goes the other way. It is here because Director Shaifudin Selamat's APEC work is real, because it shapes the firm, and because it explains the standard the rest of the operation runs to. What it does not say is the proof that the firm is the right partner for the brief that called for this case study.