A complete application in a minute
Tailored resume and cover letter, ready to send.
College Board is seeking a Security Engineer II, Endpoint Security, to own the ongoing engineering of the application allowlist, ensuring only approved software runs on managed endpoints. You will extend coverage as needs evolve, adjust policy for new device groups, and process exceptions while keeping enforcement current and low-friction for the business.
This role partners with IT, application owners, and business-unit stakeholders to maintain an accurate allowlist continuously.
This is a fully remote role. Candidates who live near CB offices have the option of being fully remote or hybrid (Tuesday and Wednesday in office). All CB employees are required to occasionally travel to meet in person for business purposes.
Full-time position
Enterprise Security Engineering (ESE) is the security team responsible for building and operating the foundational security platforms and controls that protect College Board's enterprise environment. The team owns a broad capability surface spanning security observability, endpoint security, network and edge security, data security, security review management, and AI security. ESE is both an engineering team and a standards-setting function. The team designs, builds, and operates the controls that protect College Board's workforce, data, and systems, and it owns the enterprise security standards that operationalize information security policies across the organization. The team partners across security, Technology, and other organizational divisions to deliver integrated, measurable security outcomes. ESE engineers are technical owners who drive measurable risk reduction through automation, disciplined platform operations, and continuous improvement.
As a Security Engineer II, Endpoint Security, you will own the ongoing engineering of College Board's application allowlist, ensuring only approved software runs on managed endpoints. You will maintain and extend allowlist coverage as software, vendors, and business needs evolve, define and adjust policy as new device groups come online, and process exception requests as they arise. Application allowlisting is a standing control, not a one-time project - it requires continuous engineering to stay effective as the environment changes, and you will make an immediate impact by keeping enforcement current, accurate, and low-friction for the business.
This role partners closely with IT, application owners, and business-unit stakeholders whose software needs must be captured and reflected in the allowlist on an ongoing basis.