By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Code of conduct

How we treat each other at events, in chapters and anywhere the community meets, and what happens when someone does not.

Our commitment

We want this community to be a place where anyone can learn and do this work without harassment, whatever their background, identity, body, ability, experience or employer. Everyone who takes part, including the people who run it, commits to acting in ways that keep it open, welcoming and healthy.

What we expect

  • Be kind, and assume good faith.
  • Welcome newcomers. Everyone here was new to agents not long ago.
  • Give feedback on the work, not the person, and take feedback the same way.
  • Disagree with evidence: a config, a command, a trace.
  • Own your mistakes, apologize to the people they affected, and learn from them.
  • Act for the good of the community, not only yourself.

What is not acceptable

  • Harassment of any kind, in public or in private.
  • Insults, slurs, personal or political attacks, and trolling.
  • Sexual language or imagery, and unwelcome sexual attention.
  • Threats of violence, or encouraging anyone to harm themselves or others.
  • Any other conduct a reasonable person would see as inappropriate in a professional setting.

Rules for a security community

This is a security community, and some harms are specific to it.

  • No doxxing. Do not reveal or dig up a member’s identity, employer, address or accounts they have not shared. That includes working out whose company a config came from when it was shared without a name.
  • No live exploits against members’ employers. Do not share working exploits, credentials or attack paths against a member’s employer, or against any organization that has not agreed to be tested. Discuss classes of problems, lab reproductions and fixed issues instead.
  • Disclose responsibly. If you find a vulnerability in a vendor’s agent or in someone’s organization, report it to them first, through their security contact, and give them time to fix it before you discuss it in public. Report problems with this site to security@aisecurityengineering.org.
  • Never post secrets. Redact tokens, keys, internal hostnames and internal URLs from anything you share, even if they have expired.
  • Respect what members share. Configs and incidents brought to a teardown stay in that session unless the person who shared them agrees otherwise.
  • No selling in community spaces. Do not pitch products or services to members at events, in chapters or in any community space. This applies to Vero’s staff as well. Vendors are welcome to take part as engineers.
  • Keep exam content private. Do not share lab tasks, planted findings or reference solutions. The terms of use explain what happens to a credential if you do.

Where this applies

This code applies in every community space: events, chapters, forms and email, and any channel we open later. It also applies when you represent the community somewhere else, such as speaking at a conference as a chapter host.

How to report

Write to hello@aisecurityengineering.org, or tell an event organizer or chapter host in person.

Tell us what happened, when and where, and who was involved. Include links or screenshots if you have them. If you are not sure whether something breaks this code, report it anyway.

If a report concerns someone from Vero, you can ask that no one from Vero handles it. For security issues with the site, write to security@aisecurityengineering.org. For breaches of the charter, write to charter@aisecurityengineering.org.

What happens next

We confirm we received your report. The organizers review it, and anyone involved in the report steps aside. We may talk to the people involved. We keep the reporter’s identity private, and we do not tolerate retaliation against anyone who reports in good faith.

Depending on what happened, the outcome is one of these:

  1. Correction. A private note explaining what was wrong. We may ask for a public apology.
  2. Warning. A written warning that says what happens if the behavior continues, and may ask the person to stop contacting the people involved for a time.
  3. Temporary ban. No access to community spaces for a set time.
  4. Permanent ban. No access to community spaces from then on.

Misconduct during a credential lab is handled under the terms of use and can revoke the credential. We tell the person who reported what we decided, as far as the privacy of others allows.

Attribution

This code is adapted from the Contributor Covenant, version 2.1, with rules added for a security community.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.