lfx.dev gets you to the tool suite

under "Tools" you'll see Insights which folks have been using

and Security which was discsussed last week

https://lfx.linuxfoundation.org/tools/security

Thanks, Jim.

For reference: Akraino Security sub-committee that Tina is speaking about https://wiki.akraino.org/display/AK/Security+Sub-committee

maybe add something wrt security report into the annual report elements? (thinking about Anil's comment)

https://wiki.lfedge.org/display/LE/Project+Annual+Reviews

https://bestpractices.coreinfrastructure.org/en

Some ideas proposed in TAC (no firm decisions at this stage, just suggestions):minimum requirement should be that all joining projects need to get onboarded into LX security (e.g., within 90 days of joining)in annual reviews projects must share LX security reportstage 3 projects should have a security policy and provide a limited-access email address for reporting security vulnerabilityall projects should immediately start trying the tool and providing feedback

Great summary Glen. Thank you.