Zero Trust -State Architect

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 Current-State Architect supports the CIO’s Zero Trust program by discovering, documenting, diagramming, and explaining the organization’s existing technical, functional, operational, and mission architecture. This role is part of a dedicated team of current-state architects responsible for unraveling complex As-Is environments, capturing CONOPS, interviewing stakeholders, tracing dependencies, and producing architecture drawings and baseline artifacts that accurately show how systems, data, users, devices, networks, applications, processes, and controls operate today.

The role informs future-state architects and engineering teams by providing an authoritative current-state baseline; it does not own or design the target-state architecture.

• Conduct current-state architecture discovery on a service-by-service and organization-by-organization basis, documenting mission workflows, legacy systems, applications, data flows, infrastructure platforms, interfaces, security tools, and operational processes. Map validated findings to the Zero Trust pillars to assess alignment, identify gaps, and inform program baseline development.
• Develop clear architecture drawings, dependency maps, interface diagrams, system context diagrams, workflow views, sequence maps, and CONOPS products that explain how the current environment operates.
• Interview system owners, mission stakeholders, engineers, operators, security teams, and program personnel to collect, validate, and reconcile fragmented or undocumented architecture information.
• Investigate and reverse-engineer undocumented interfaces, data exchanges, access paths, operational dependencies, control points, and business logic across distributed, hybrid, and legacy environments.
• Capture As-Is CONOPS, operational scenarios, user journeys, mission threads, handoffs, decision points, data movements, system interactions, and sequences of interaction in a format that can be used by future-state architects and program leadership.
• Build and maintain current-state architecture artifacts using MBSE, enterprise architecture, diagramming, and collaboration tools as appropriate for the program.
• Identify architecture gaps, unknowns, technical debt, lifecycle risks, undocumented dependencies, single points of failure, and modernization considerations discovered during current-state mapping.
• Provide validated current-state findings, diagrams, CONOPS products, and baseline artifacts to future-state architects, engineering teams, governance bodies, and program leadership to support target architecture planning and implementation decisions.

• Working knowledge of Zero Trust principles, IC and DoD cybersecurity environments, enterprise architecture concepts, system-of-systems dependencies, current-state baseline development, and operational architecture capture.
• Knowledge of the Department of Defense Architecture Framework (DoDAF) and Unified Architecture Framework (UAF), including their use in developing and communicating operational, systems, services, data, and capability architecture views.
• Knowledge of CONOPS…