Zero Trust Advisor

Description

Pueo is known for bringing the best talent and unique tools to every opportunity. Pueo's Parliament (aka workforce) is composed of professionals who are seeking the opportunity to work in a business organization that thrives on career development and independence. In support of mission and professional growth, our Parliament has supported the development of multiple patents, proprietary tools, and applications as well as trademarked processes.

Our organization emphasizes career development across multiple career environments (at the members own pace) and ensures those who contribute broadly are properly rewarded. Pueo has four career environments where every member of the parliament can participate. Each environment has opportunities available for all levels. Opportunities are framed by an employee's desires and capabilities, and we ensure challenges, growth, and unique experiences are available for employees at all levels.

Our Career Environments (Program, Functional, Service, and Leadership) provide numerous opportunities for employees to invest in their personal growth and those things that offer fulfillment. We invest in helping our members create and execute their career development plans. Our Pods (small teams of 5 or less) are comprised of personnel with similar skillsets to ensure mentorship, understanding, and peer support.

The Zero Trust Application Advisor serves as a principal technical liaison, application domain expert, and technical advisor supporting the CIO’s Zero Trust Program and the wider Defense Intelligence Enterprise. This role is dedicated to partnering with and shepherding application owners through the Zero Trust landscape and functional requirements by explaining the  what  and the  why  to articulating the security intent and clarifying exactly what must be done to meet issued Zero Trust functional requirements and protocols before applications enter formal accreditation and onboarding to the JWICS network.

The Advisor does not govern applications or dictate implementation timelines and mechanics, leaving the  how  (engineering design and technology selection) and the  when  (development schedule and release planning) to the respective application teams. The Advisor does not code, script, implement solutions, govern application roadmaps, or dictate technology choices, engineering methods, schedules, or releases; application teams retain those responsibilities.

• Guide application owners through pre-accreditation readiness, explaining mandatory functional criteria, compliance evidence, and submission gates.
• Review architectures, data flows, API specifications, interfaces, and identity integrations against CIO-issued ZT requirements, the DoD ZT Reference Architecture, and IC security baselines; document gaps and actionable advisory findings.
• Translate ZT objectives into developer-ready functional requirements, acceptance criteria, and checklists covering workload identity, mTLS, API security, least privilege, and continuous verification.
• Recommend architectural alternatives, interim mitigations, compensating controls, and technical workarounds for legacy, proprietary, or third-party constraints without implementing changes.
• Build relationships with application owners, developers, architects, and program managers; facilitate technical exchanges, workshops, and readiness reviews to resolve integration challenges and connect delivery teams with enterprise cyber leadership.
• Coordinate alignment with enterprise identity, device/workload posture, data tagging and protection, network segmentation, and telemetry/SIEM services; advise on common controls and inherited capabilities to reduce RMF/ATO preparation burden.
• Escalate persistent architecture bottlenecks, ambiguous requirements, and unresolved integration risks to senior ZT architects and program leadership with recommended actions.

• Identity and access:
  Workload identity and attestation (e.g., SPIFFE/SPIRE), mTLS, secure credentials, PBAC/ABAC, and continuous request/API verification.
• API interoperability:
  Gateway integration, token and schema validation, rate limiting, and secure REST/gRPC exchanges across JWICS enclaves.
• Secure delivery:
  Dev Sec Ops  security checks, vulnerability mitigation, and software-component transparency for JWICS readiness.

• ZT principles and federal guidance: NIST SP 800-207, OMB M-22-09, DoD ZT Strategy and Reference Architecture, and…