Purpose
A Technical Guidance Contributor provides practitioner insight, experience, and perspective to help develop peer-to-peer cybersecurity guidance. Technical Guidance Contributors help identify relevant topics, share practical examples, review draft content, and ensure the paper reflects real-world professional judgment rather than abstract theory or institutional messaging.
Responsibilities
A Technical Guidance Contributor may contribute to some or all the following areas, depending on availability and interest:
- Supporting the development of practical guidance, decision points, considerations, and professional judgment factors rather than prescriptive organizational policy.
- Participating in topic discussions and contributing ideas that reflect current cybersecurity challenges, practitioner concerns, and emerging areas of professional practice.
- Sharing practical experience, examples, lessons learned, and resources that may help other cybersecurity professionals understand how a topic applies in real-world environments.
- Helping ensure the Technical Guidance paper maintains a peer-to-peer voice, focused on what cybersecurity professionals should know, consider, or apply in practice.
- Identifying gaps, unclear sections, technical inaccuracies, or areas where additional context, examples, or references may improve the paper.
- Helping preserve the distinction between volunteer practitioner insight and official ISC2 policy, certification guidance, or institutional positions.
- Reviewing draft Technical Guidance content for clarity, accuracy, relevance, and usefulness to practitioners.
Expectations
To promote meaningful collaboration and efficient use of time and resources, Technical Guidance Paper Contributors are expected to:
- Attend and actively participate in scheduled virtual workshops of varying sizes.
- Complete assigned work by requested deadlines.
- Contribute thoughtfully and respectfully, representing broader membership and profession rather than personal interests.
- Exhibit integrity and professionalism in line with the ISC2 Volunteer Code of Conduct.
- Communicate promptly and share availability preferences to help ISC2 effectively align work with individual capacity and coordinate scheduling.
ISC2 Membership Requirement
Yes
Qualifications/Skills Required
- Must hold an ISC2 certification and be a member in good standing.
- Cybersecurity expert with a passion for writing and research.
- Firm understanding of business-level English. This requires the ability to read, write, and speak in meetings on technical topics with other SMEs exclusively in English.
- Passion for advancing the global cybersecurity profession through learning and development.
- Commitment to upholding ethical and editorial standards.
Training
Some training may be required.
Travel Requirement
No travel is required.
Start/End Date
Technical Guidance is developed on a quarterly basis, with workshops held throughout the year depending on the area(s) of focus. Selected Technical Guidance Contributors will be notified in a timely manner regarding scheduling and any expectations.
CPE Credit(s)
CPEs will be issued based on attendance and work completed, in accordance with the ISC2 Certification Maintenance Policy and Handbook.
CPE Submission Process
ISC2 will submit CPE credits earned on behalf of the volunteer.
Benefits
- Contribute to the advancement and professionalization of the global cybersecurity profession.
- Network and meet others from within the ISC2 community.
- Earn CPE credits.
- Add volunteer experience to your resume/CV.
- Able to volunteer from home.
Reference Materials
Provided as needed.
Contact
guidanceteam@isc2.org
Register Interest
Register