The scope of this seat will include, but not be limited to:

• The role of the security and observability SME is to work with project TSCs, the TAC, and the LFNGB to improve the security of the code produced by LFN projects and to advance the use of open source technology for building a holistic observability framework with best practices encompassing network fabric.

  1. Implementing more secure software development culture:

     1. Secure software development best practices and tools (e.g. from the survey table),

        • Software development best practices and tools that decrease the vulnerabilities in LFN project code (code scanning, package upgrades),

        • Software supply chain security best practices (SBOM, code/container signing) to increase the security transparency of LFN project code,

        • LFIT security practice improvement,

        • OpenSSF badging assistance.

     2. Identify cross open source project security issues and provide action recommendations.

     3. Keep track of regulatory cyber security requirements (such as US gov security mobilization plan and EU Cyber resilience act) and identify touch points for LFN projects.

     4. Providing subject matter expertise to the TAC.

     5. Advising the TAC on security related issues.

  2. Network Observability: Serve as the primary architect for how telemetry, monitoring, and analysis evolve across our ecosystem. The role is to ensure that LFN projects don't just "generate data," but provide the deep, actionable insights required for modern automated networking.

     1. Horizon Scanning & Technical Research: Proactively track global developments in observability (e.g., eBPF, OpenTelemetry, Flow-based analysis, and AI-driven anomaly detection). Evaluate how "state of the art" cloud-native observability patterns can be effectively translated to complex networking environments like RAN, Core, and Edge.

     2. Standardization of Best Practices: Develop and maintain a comprehensive set of observability best practices for LFN. This includes defining consistent schemas for logs, metrics, and traces to ensure interoperability and a unified "single pane of glass" experience across different open-source networking stacks.

     3. Cross-Project Technical Guidance: Act as a hands-on consultant for LFN projects . Provide architectural reviews and guidance to help project maintainers integrate observability frameworks natively into their codebases, moving the ecosystem toward "observability by design."

     4. Strategic TAC Briefing: Serve as the bridge between the observability community and LFN leadership. Provide regular, high-level briefings to the Technical Advisory Committee on emerging trends, potential gaps in the LFN portfolio, and strategic recommendations for new project pivots or partnerships.ject pivots or partnerships.

Election Mechanics

How to nominate yourself

The election process occurs in two phases: the Nomination phase and the Election phase.

Self Nomination Phase

Individuals interested in running for this position must edit this wiki page with their biography and statement of intent on why you would be a good person to hold this position (Information on Candidates)

The nomination phase starting Feb 18, 2026 and will conclude on Mar 4, 2026  18:00 PT (02:00 UTC). 

Election Phase

If multiple nominees come forward, an election will be conducted as follows:

• Voting Method:

  • A Condorcet election using a ranked-choice voting platform administered by the Linux Foundation.

• Voters:

  • All TAC members will receive an invitation to vote via email.

• Timeline:

  • The election phase will begin with the distribution of the voting instructions.

  • Voting will remain open for four (4) full business days from the time the poll is initiated (typically in the PDT time zone).

Information on Candidates

Name: Tony Hansen

Photo <optional>:

Open

Company: AT&T

Short Biography: I’ve been working with LFN as part of the ONAP community since 2017, both as part of the Security Sub-Committee and as a code contributor. I have long been a proponent for the OpenSSF Best Practices badging project and am a member of the Technical Steering Committee there. I’ve been in the industry (Bell Labs, AT&T Labs) for 45+ years.

Statement of Intent: I intend to continue my work in the ONAP security sub-committee, but in the broader scope of the LFN. There are so many things we learned in ONAP that be extended into other LFN projects.

Name:

Photo <optional>

Company:

Short Biography:

Statement of Intent: