![]() | |||||||||||
|
| |||||||||||
|
Membership
GoalDevelop a trusted community for sharing information regarding cybersecurity threat, incidents, response, and protection, specifically designed to support the unique environment and needs of higher education and research organizations. The trust community will provide a forum for sharing sensitive information, a source for trusted contact information, a meeting point for peers, a means to facilitate communications, and methods for improving cybersecurity awareness and response. Membership Criteria
Examples that illustrate membership eligibility are included at the bottom of this document. Applying for MembershipMembership requests are put to the current members for vouching. There are two ways of applying for membership: Normal and Sponsored. The distinction is only to the method of establishing membership - there is no subsequent distinction of trust and information sharing. Normal Membership: Two current REN-ISAC members must vouch that the applicant meets membership criteria, with no members dissenting. Sponsored Membership: Relies on the single vouch of a sponsor, with no members dissenting. To facilitate the membership of select, trusted subordinates of existing REN-ISAC members - when the subordinate doesn't have recognition within the community - an existing member can sponsor the application of a subordinate. The subordinate must meet all Membership Criteria, but requires no additional vouches. The Sponsored Membership request will be put to the members for question and dissent. Whenever possible the Normal Membership method should be used. To apply for Normal Membership, the applicant sends a request to:
To apply for Sponsored Membership, the sponsor sends the above information on behalf of the subordinate, and indicates that it's a sponsored request. Changes in a Member's Employment Status or ResponsibilitiesMembership is tied to the individual's organizational representation and responsibilities. If an individual terminates or changes employers, the membership must be immediately terminated and, if appropriate, the individual must reapply as a representative of the new organization. If an individual changes responsibilities within an organization and no longer serves in a capacity that meets the Membership Criteria, the membership must be immediately terminated. Members should promptly report changes in their employment as effects membership eligibility. Membership Confirmation and TerminationTrust is established and maintained through published and rigorously enforced membership criteria and active maintenance of the member roll. REN-ISAC will aggressively poll the membership for confirmation of status. Members must respond to the confirmation requests or membership will be terminated. REN-ISAC may at its discretion reissue vouch requests, either privately or to the membership mailing list, to confirm a member's standing. REN-ISAC reserves the right to unilaterally terminate the membership of an individual without notice. The member roll will be visible to members via the review command of the renisac-sec-l listserv. Ex Officio MembersCertain persons who don't meet the Membership Criteria may be granted membership by virtue of their position. For example, members of the REN-ISAC Technical and Executive Advisory Groups, technical directors of sponsoring organizations, etc. Ex Officio memberships will be granted at the discretion of the REN-ISAC. Membership Eligibility ExamplesAnn is the lead sysadmin for a number of institutional servers that support the primary financial and student systems of the university. She is specifically tasked with security for the systems. Although she has explicit security responsibilities in her job description, she doesn't meet the requirement #4 to "represent security for the institution." Ann is not eligible for membership. Mel is an IT support provider in the College of Arts and Sciences at the University and spends greater than 50% of his time on security matters for the College. The University has a central IT organization including a central security team. Mel is not eligible because he doesn't meet the requirement #4 of having security duties "across the institution in whole or substantial part." Kyle is part of a three-person team handling security incidents for the University. The team is composed of students who rotate duty according to their class schedules. Kyle is not eligible for membership because he doesn't meet the requirement #3 for permanent staff. Cheryl is a network engineer in the NOC who spends 50% of her time working on security matters that affect the entire University. Security incidents are referred to her from the University IT Security Office - she works at the direction of the security office. Cheryl is not eligible for membership because she doesn't meet the requirement #3 to have a principal responsibility in security protection and response. Meryl (Cheryl's older sister) is a senior network engineer in the NOC at a different University. Like Cheryl, Meryl spends 50% of her time working on security matters. Although the University has a separate IT Security Office, Meryl is tasked to work independently and in conjunction with the Security Office for network security matters. Meryl is eligible for membership because she shares principal responsibility for security protection and response.
Page Revised: June 19, 2006
| ||||||||||