Past Meetings

October 2026 Videoconference

Official minutes of this Board meeting.

Meeting Details

  • Date: Wednesday, November 4, 2026
  • Time: 5:00 PM PST – 6:30 PM
  • Location: In person at Global Appsec USA 2026, San Francisco, CA, USA

Call to Order

  • Steve Springett - PRESENT

  • Ricardo Griffith - PRESENT

  • Harold Blankenship - PRESENT

  • Sam Stepanyan - PRESENT

  • Ashwini Siddhi - PRESENT

  • Marisa Fagan - PRESENT

Kelly Santalucia was absent, and gave apologies prior to the meeting to the Chair.

Board Members

  • Ricardo Griffith — Remote
  • Steve Springett
  • Harold Blankenship
  • Sam Stepanyan
  • Ashwini Siddhi
  • Marisa Fagan

Absent

  • Kelly Santalucia — Apologies given prior to the meeting

The Board had quorum

Guests

  • Andrew van der Stock — Remote
  • Lori Meagher
  • Chris Barbeau — Apologies - meeting is out of hours
  • Leea Hudson-Wilson — Apologies - meeting is out of hours
  • Michael Koppmann — Director-Elect. Remote
  • Diego Silva Martins — Director-Elect. Remote

Conflict of Interest and Anti-Trust Statement

As the Board consists of individuals from many competing organizations, OWASP and its Board shall abide by all applicable anti-trust and competition laws. To avoid any perceived or actual conflict of interest, or anti-trust concerns under US federal, state, or regulations, only the published agenda shall be discussed or voted upon, or amended as below. If there are any conflicts of interest, Board members are expected to disclose the conflict of interest and must recuse themselves from discussion and voting.

No conflicts were declared

Changes to the Agenda

Changes to the agenda - unless otherwise prohibited by anti-trust or competition laws - including adding, altering, or tabling of motions is permitted by following Roberts Rules of Order (RONR 12th Ed) 41:63, which requires an affirmative two-thirds vote.

No changes to the agenda were made.

Minutes were approved

  • Steve Springett - YES

  • Ricardo Griffith - YES

  • Harold Blankenship - YES

  • Sam Stepanyan - YES

  • Ashwini Siddhi - YES

  • Marisa Fagan - YES

Minutes passed 6-0. Kelly Santalucia was absent.

Approval of Minutes

Pre-reading Material

Reports

Management Report and Finance Report

The Executive Director presented the new, more compact format of the Board oversight report, together with the Foundation and Finance board summaries, the finance summary and full management report videos, the cash flow forecast and the aged receivables report. No director had questions on the slides.

Audit and Form 990. All audit materials have been delivered. A first draft of the Form 990 is available, with filing planned for 15 November. The Executive Director will share it with the Audit Committee (Steve, Harold and Ricardo asked to be included) and will present it to any other director on request.

People. Grant Williams (Atlanta) and Diego Cotelo (Uruguay) have joined staff. Diego will run IT automation and look after IT assets. The Executive Director is looking at implementing an ISMS under ISO 27001 and updating the risk register to ISO 31000, with a meeting with Fabio the following week. Succession planning is in progress and will incorporate Diego's role.

Elections and bylaws. The 2026 election results were presented. Harold Blankenship, Michael Koppmann and Diego Silva Martins were elected; the Executive Director thanked Patrick Dwyer, who was unsuccessful, and encouraged him to stand again. Harold will continue supporting a transition period. The next steps are induction training and pre-reading, background checks, and then the conflict of interest and Director's Commitment Agreement signatures. Ricardo and Ashwini were thanked for their service; this was not their last meeting.

Turnout was 657 voters from 5,330 eligible members (about 12.3%). 128 members were unsubscribed and so did not receive a ballot, 123 ballot emails bounced, and one recipient marked the ballot as spam. Turnout has trended down since 2021 apart from a rise last year, despite the same number of email blasts and more social media promotion. The election also raised issues that the Foundation's lawyers are reviewing, together with certificate of incorporation issues that currently block grant-making and fundraising. An update will be given at the November Board meeting.

Finance and operations (Lori Meagher). Receivables were $713,000 on 13 September; $284,000 of past-due receivables has since been collected, $57,000 of it over 90 days old. Charity CFO is reviewing a proposal to move accounts payable into Bill.com, targeted for 1 January. A $100 internal de minimis policy for missing receipts on small expenses has been agreed with Charity CFO; approvals and controls are unchanged. The corporate card is moving from Charity Card (Commerce Bank) to Chase One Card, now in underwriting. The idle Citizens Bank checking account will be closed, keeping the money market account. The FY2027 draft budget will come back to the Board before the end of November.

Finance summary (Charity CFO, September 2026). Cash on hand was about $1.95 million, up $71,000 from August, equal to 4.6 months, with a current ratio of 17:1 and net assets of $3.4 million. Year-to-date net income was $901,000, with revenue of $4.6 million (about 20% over budget) and expenses of $3.7 million (just under 4% under budget). 53% of revenue came from sponsorships and 84% from conferences. Cash will fall as US conference bills are paid; the cash flow forecast is in the Board materials. Questions for Charity CFO can be put on notice to the Executive Director, with answers in a couple of days.

Website and security. Features needed for the Meetup migration are live. The website code will be open sourced after the Git history is squashed to remove an accidental check-in of seed user data. The old wiki is offline; Harold exported about 130,000 articles to preserve as archive.owasp.org at Sam's request, but Cloudflare's 100,000-file hosting limit needs a workaround. Microsite droplets were disabled and projects using WordPress asked to patch. GlueUp reported a PHP shell issue but had no breach. Website dependencies were updated and a Dependabot rule added.

Service desk and events. Most queues are healthy; project tickets are slowest because of the project committee approval step, and payments processing drives the longest-open finance tickets. The Executive Director highlighted Lauren's slide on rising event costs, which will need discussion on pricing; Atlanta is a lower-cost venue than San Francisco, and attendance at Vienna and this year's events is encouraging. Work on the EU Cyber Resilience Act (CRA) continues as a top priority. Registration numbers for this conference were not available and will be sent to the Board after the meeting.

New Business

Committees Update

The Board discussed the effectiveness of member committees, following a longer discussion at the previous day's private Board meeting. Apart from the Events Committee, which a member in the room said is working well, and the newly reformed Chapter Committee, which has not yet had time to meet, most committees are inoperative, not meeting or not delivering. The Projects Committee is inactive under policy: it has given no quarterly updates and held no elections. The Committees Policy is out of date, has conflicting language, and under it none of the committees would count as active. The Board already has an outcome-driven Working Groups Policy, and committees and working groups are listed on the website under About.

The Chair stressed that the later vote is not a negative reflection on committee members; its aim is to remove unnecessary process so volunteers can focus on their work. The Executive Director said this is the third attempt at committees and that the 2027 Board will meet in January to develop a replacement policy with leader feedback. The Events Committee will continue as a working group for 12 months. A director who previously chaired and liaised with the Chapter Committee noted that committees need sustained commitment, that minimum-membership rules were hard to meet, and that committees give volunteers mini-board experience and suit standing functions that working groups do not. The committee policy question should go to the next Board meeting and to the incoming Board.

In answer to a question about how project promotions will proceed without the Projects Committee, the Executive Director said staff will apply the committee's existing promotion and demotion guidelines directly, with an appeals process, as staff can dedicate about 40 hours a week against the committee's one to two hours a month for 300-plus projects. This should clear the backlog. A future project working group can then address strategic items, including the open letter from about 2021 or 2022 and the Board's strategic plan.

The Executive Director reported that the new Project Handbook, replacing the 2014 version, is nearly ready, drafted by Starr from the project leaders' earlier version. It will be hosted in Confluence so the community can keep it evergreen, and the Chair stressed that it must be community-authored and reviewed by project leaders before release.

Policy Review Status Update

Community Review Process - Ricardo

With the review team; comments are moving back and forth. Ricardo will confirm their expected completion date, then address the feedback.

Committees Policy - Harold

Was near completion, but given the decision to redo the policy it needs a fresh critical review; deferred to the 2027 Board.

AI Policy - Andrew and Ashwini

Over 80 community comments received. To be incorporated, then sent to the policy review team for finalisation.

Social Media Policy - Ashwini

Mostly complete and open for review. Comments focus on personal accounts; the wording will be reframed to make clear it protects the OWASP brand and prevents abuse, not to curb personal freedom or monitor accounts. It will return to community review, with completion hoped for by December.

Code of Conduct / Code of Ethics - Marisa

In the creation phase. The Code of Conduct will cover attendees of events and social spaces; a new Code of Ethics will cover members.

Bylaws and certificate of incorporation. The Executive Director reported that he and Ricardo had planned to tidy the bylaws this year. He has given the lawyers feedback on issues found in the election, so a new set of bylaws may result. Open points: whether the bylaws and certificate must go through community review, as the changes mostly tidy up issues found in the election; aligning the Members Policy with the bylaws, which take precedence over any policy; and the Delaware requirement for proxy voting, which the current voting platform does not support. The Executive Director is taking legal advice.

Ballot delivery. In discussion of the 128 unsubscribed members who did not receive ballots, the Executive Director said the ballot email is business-essential communication that should not be subject to an unsubscribe link, and that unsubscribe choices were carried over from previous imports. Because elections are held electronically under the bylaws, with a single transferable vote and a unique ballot per member (not supported by GlueUp), a new voting platform may be needed, supporting proxy voting if required. The Chair said these questions, and how to raise the turnout of about 12% (it was upwards of 25% at one point), belong on the January agenda. He invited anonymous feedback from members on why people do not vote and will speak to former Board members next year to inform future Boards.

Sponsor: TBA · Second: TBA

DIscussion of Draft Budget

The draft FY2027 budget was not shown on screen because it was not in a presentable format and contains detailed salary information; directors saw an initial draft at the previous day's private meeting. Lori Meagher described the process: the FY2026 budget and year-to-date actuals were annualised to project the year-end position, and the events team prepared its budgets. Still outstanding are the projects division numbers and final operational expenses. Staff will meet teams in the coming weeks to improve revenue lines and tighten expenses, and will present a more reasonable budget to the Board by the end of November.

The draft includes OCSD but does not yet include the WISP. OCSD was deferred to other business to avoid amending the agenda.

Slack and GlueUp spam and community moderation discussion

The Executive Director reported that GlueUp moderation must remain with staff, because making someone a GlueUp administrator gives them access to everything. Slack moderation can be opened to the community. Because the Foundation's nonprofit Slack plan cannot require new users to accept terms and can restrict only one channel, the community Slack landing channel has been restricted for about a month, at the cost of its use for announcements. Anyone can join the Slack by invite link, and some joiners promote their own startups, solicit contributors to non-OWASP projects, send DM spam or behave maliciously.

The Chair suggested a click-through form acknowledging the Code of Conduct before the Slack invite is issued, and a pinned post on the GlueUp discussion board reminding members of the rules. Missie has contacted three promoting companies that came to staff's attention; the Executive Director asked the community to report such cases and tag her. A director suggested assuming good intent and treating this as an opportunity to invite them to become corporate supporters.

Directors urged everyone to help new people find the right channel, respond quickly and politely, and use the existing spam emoji, which triggers automation after five reactions. Content Moderation and Content Moderation Public Slack channels exist, along with discussion channels for projects and chapters and a Meetup migration channel.

The Executive Director plans to have volunteer moderators, with any leader eligible, sign a social media agreement, aiming for 24/7 coverage. Several volunteers are ready. A director asked that moderators be drawn from a variety of time zones; the Executive Director agreed. No policy change is needed beyond the Social Media Policy and Code of Conduct drafts, on which he will comment. No vote was taken.

Meetup Sunset Discussion

The Executive Director reported that the Foundation must be out of every Meetup group other than the OWASP Foundation group by 15 January 2027, and asked that no Meetup events be created after that date, since attendees could not RSVP. January and February meetings should be created on the new website, which now supports hybrid and in-person meetings, RSVP limits, attendee lists, notification emails when a meeting moves or is deleted, calendar invites in the attendee's time zone, and standing meetings for chapters, projects and working groups. Printable attendee lists for security desks are still to be built, and standing-meeting RSVPs may need to clear each month; the Executive Director will take feedback on both before cutover.

The key work is communications, delivered in waves. A public migration page is maintained, and Starr will lead the discussion at the Leaders Meeting the next day, which the Executive Director cannot attend. Leaders should secure control of their owasp.org chapter or project page and pin a migration notice or banner on their Meetup page. Legal advice is being obtained on whether the Foundation may export Meetup members' email addresses and contact them.

Sam raised the tight timeframe and asked whether the Foundation's co-organiser account on every Meetup group could send the announcement automatically. Neither the Executive Director nor Harold knew whether Meetup's GraphQL API allows messaging or updates; the Executive Director will ask Diego to investigate. The Executive Director hopes to automate listing owasp.org events on the single OWASP Foundation Meetup group so events stay discoverable, subject to what the API allows. The Executive Director will update the Board at the November, December and January meetings.

Motion to rescind Events policy and events timeline policies

The Chair explained that the two events policies are operational in nature, and that the 2027 Board will revisit whether any policy elements are missing and should be addressed in a future policy.

Motion: Resolved that all events-related policies are rescinded in favor of an updated Events handbook and operational procedures.

Sponsor: Steve Springett · Second: Harold Blankenship

  • Steve Springett: YES
  • Ricardo Griffith: YES
  • Harold Blankenship: YES
  • Sam Stepanyan: YES
  • Ashwini Siddhi: YES
  • Marisa Fagan: YES

Vote: 6-0 Motion passed unanimously.

Kelly Santalucia was absent with apologies.

Rescinding and dissolving all Member Committees

The Chair read the rationale: the current committees under the Committees Policy have not delivered strategic outcomes and have often focused on operational deliverables that staff can handle more effectively. Effective committees, such as the Events Committee and the newly formed Chapter Committee, will temporarily move to working groups. Other active committees may establish working groups until a future Board redrafts a committee policy.

Motion: Resolved that, effective immediately, the Committees policy is rescinded and all Member Committees are dissolved. This does not affect Board committees, such as the Audit Committee. The OWASP Foundation will stand up Events and Chapter working groups. Other active committees are welcome to establish working groups in accordance with the working group policy.

Motion: Resolved that, effective immediately, the Committees policy is rescinded and all Member Committees are dissolved. This does not affect Board committees, such as the Audit Committee. The OWASP Foundation will stand up Events and Chapter working groups. Other active committees are welcome to establish working groups in accordance with the working group policy. "

Sponsor: Marisa Fagan · Second: Steve Springett

  • Steve Springett: YES
  • Ricardo Griffith: YES
  • Harold Blankenship: YES
  • Sam Stepanyan: YES
  • Ashwini Siddhi: YES
  • Marisa Fagan: YES

Vote: 6-0 Motion passed unanimously.

Kelly Santalucia was absent with apologies.

Comments, Announcements, and Other Business

OCSD certification and other project updates (Shruti Kulkarni). The curriculum documentation, supplementary reading and OWASP reference materials for the certification program are complete. A project demo will invite volunteers, especially developers, to review the curriculum, followed by an exam question bank so people can start taking the exam; the Board will be among the first to sit it. For the London training event, there will be no February 2027 event after lessons learned from February 2026; the team is looking at the first week of October 2027, is deciding between two venues and will visit after returning to London. Sam can help with sponsorship. Separately, three modules of an information risk assessment curriculum project are ready for universities and the project is seeking contributors, who can contact Shruti at sruti.kulkarni@owasp.org.

Private session with Grant. The Executive Director asked whether the Board had met Grant privately for the compliance update planned on the previous day's agenda. It had not, as it cannot be held in the public session. The Executive Director said he need not attend and is aware of the results, and Lori may attend if the Board wishes.

Adjournment

Adjournment motion

The next general Board meeting is on November 24, 2026, at 12 pm US Eastern Time.

"It is moved, and seconded to adjourn. Those in favor, say "aye""

Sponsor: Chair Second: TBA


Sponsor: Steve Springett · Second: Ricardo Griffith

There were no other announcements or business. The Chair noted the meeting was finishing 12 minutes ahead of schedule. It was moved by the Chair and seconded by Ricardo Griffith to adjourn, and the Board agreed by voice vote.

The next general Board meeting is next general Board meeting is on November 24, 2026, at 12 pm US Eastern Time..

OWASP Logo
OWASP is a nonprofit foundation improving software security through open-source projects, global communities, and education. All resources are free and open to everyone.
OWASP, the OWASP logo, and Global AppSec are registered trademarks and AppSec Days, AppSec California, AppSec Cali, SnowFROC, OWASP Boston Application Security Conference, and LASCON are trademarks of the OWASP Foundation, Inc.
© 2026, OWASP Foundation Inc. All rights reserved.