Focus areas

Where the guild puts its time.

Four areas, chosen because a volunteer network can genuinely move them and because they matter to the organisations already inside Global Tech Advocates.

01

Practitioner exchange

A standing forum for security people across GTA networks. Closed-door sessions where practitioners can be candid about incidents, tooling that did not work, and decisions they would take differently. Chatham House rules by default.

Value here comes from frequency and trust rather than production values. A recurring call with fifteen of the right people beats an annual conference with three hundred of the wrong ones.

02

Expertise on call

GTA has more than forty networks and tens of thousands of members. Security questions surface constantly: a founder facing their first enterprise security questionnaire, a chapter planning an event on AI risk, a policy consultation with a short deadline.

The guild is where those requests land and get matched to someone qualified and willing. Not a consultancy and not free labour for member companies, but a route to a considered answer from a peer.

03

Raising the floor

Most organisations in the network are small, and many have no security function at all. The gap between nothing and basic competence is where the most risk sits, and it is closed with plain guidance rather than specialist depth.

Practical material aimed at founders and operators: what to do first, what can wait, what the questions in that enterprise questionnaire are actually asking. Vendor-neutral, including where our own sponsors compete.

04

A voice in policy

Global Tech Advocates exists to give tech a voice worldwide. Cybersecurity regulation is being drafted quickly in many jurisdictions at once, frequently without much contact with the people who will have to implement it.

The guild can convene practitioner input on consultations and supply evidence grounded in operational reality. GTA already does this through the Chips Coalition and similar efforts; the mechanism is proven.

Deliberately not

Things the guild will not do

  • Certify or accredit anybody. There are enough badges. The guild has no standing to issue one and no wish to.
  • Compete with its own members. Many members sell security services. The guild does not bid for work, and does not become a procurement shortlist.
  • Run an incident response service. If a member is in trouble at 2am, the guild is not the number to call, and pretending otherwise would be dangerous.
  • Publish threat intelligence as a product. Sharing between practitioners is one thing. Becoming a feed with a name is another, and is not what a volunteer guild should take on.

Saying no to these keeps the guild credible with the people whose participation makes it work.

Shape what comes next.

These four areas are a starting position, not a settled programme. The members who turn up in the first year will decide what the guild actually becomes.

Get involved