Skip to main content

How to join

OK-ISAC Services and Capabilities

Provide members:

  • Access to monthly statewide cybersecurity briefs.
  • Real-time threat intelligence sharing.
  • Participation in conferences, workshops and tabletop exercises.
  • Supports efforts to enhance cyber workforce development.
  • Develops and maintains relationships with industry partners.
  • Supports members through implementing best practices and establishing a culture of cybersecurity and compliance.

Requirements

OK-ISAC was created to assist in sharing cyber threat intelligence among its members to increase cybersecurity readiness and response efforts in Oklahoma. These efforts include but are not limited to, disseminating cyber threat intelligence, sharing security incident information between members, and distributing industry-recognized security practices.

Organizations requesting membership must be Oklahoma-based or have direct relationships with Oklahoma Cyber Command. The individual requesting membership for their organization must be full-time staff having or sharing the principal responsibility for security protection and response at their organization. All individuals are required to have an email address associated with the member organization for which they are providing cybersecurity services for.

OK-ISAC will be a community built on trust among members due to the sharing of sensitive information regarding cybersecurity threats, incidents, response, and protection. This established trust will allow members to safely share information without concern that the information will draw unwanted attention to their organization. Individuals participating in OK-ISAC are required to accurately represent themselves, reliably act in the interests of their organizations and promote a cybersecurity culture in Oklahoma.

Data sharing protocol

All data provided by OK-ISAC or any member shall include an information-sharing designation following the US-CERT Traffic Light Protocol (TLP), as set forth below.

If data is shared without a TLP designation, it is automatically treated as TLP Red unless the entity sharing the data later specifically changes the designation.

Last Modified on Sep 10, 2024
Back to Top