Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Zero-Trust Architecture Migration Planner

    1

    Generate a phased, low-disruption roadmap to migrate legacy network topologies to a Zero-Trust security model.

    $4.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Zero-Trust Architecture Migration Planner

    Zero-Trust Architecture Migration Planner

    Example session with this skill installed

    {{legacy_network_topology}}: Flat network structure with VPN-only remote access, on-prem Active Directory syncing to Entra ID, legacy Cisco ASA firewalls, unmanaged BYOD laptops, and shared service accounts for database access. {{business_critical_systems}}: ERP system (SAP on-premise), Customer Support Portal (AWS hosted), and internal file servers (Windows Server 2016).

    • Read your context and instructions
    • Compiled the zero-trust architecture migration

    Zero-Trust Migration Plan

    1. Threat & Vulnerability Assessment

    • High-Risk Endpoints:
      *

    Unmanaged BYOD laptops: These have no posture checks or patching guarantees, and once on VPN they sit inside the flat network, so a single infected laptop reaches everything, including SAP and the file servers.
    *

    Shared database service accounts: Credentials are shared by people and applications, so there is no attribution and rotation is hard. A compromise gives direct access to SAP and portal data.
    *

    Flat internal network: There are no east-west controls, so any foothold allows unrestricted lateral movement (scanning, SMB/RDP pivoting, credential relay).
    *

    Legacy Cisco ASA firewalls and VPN: They provide perimeter-only trust and network-level access once authenticated. Check model and software end-of-support status and patch level, since VPN appliances are a frequent initial-access target.
    *

    Windows Server 2016 file servers: Extended support ends in January 2027, about two months from now. They are likely to hold sensitive data and use legacy protocols (SMBv1/NTLM) that are exposed on a flat network.
    *

    Hybrid identity (on-prem AD ↔ Entra ID sync): Compromise of AD or the sync server can escalate into the cloud tenant, and from there to the AWS-hosted portal.

    • Access Blind Spots:
      • VPN success is treated as proof of trust, with no device health, location or behavior evaluation.
      • Shared accounts make auditing impossible, so you cannot tell who accessed what.
      • Legacy authentication (NTLM, basic auth, LDAP simple binds) likely bypasses MFA and Conditional Access.
      • No visibility into BYOD software state, data stored locally, or sessions to the AWS portal.
      • Privileged AD accounts probably lack tiering, just-in-time elevation and session recording.

    2. Zero-Trust Migration Roadmap

    Phase 1: Identity & Device Verification (0-30 Days)

    Inventory and baseline: Pass-through traffic flow mapping (NetFlow/ASA logs) to document who and what talks to SAP, the file servers and the database tier. Catalog all service accounts, owners and dependent applications.
    *

    Enforce MFA everywhere in Entra ID: Use phishing-resistant methods (FIDO2/passkeys) for admins and Authenticator number-matching for everyone else. Roll out in report-only Conditional Access first, then enforce in waves, pilot group first.
    *

    Block legacy authentication: Audit sign-in logs for basic and legacy protocol use, remediate dependent apps, then block through Conditional Access.
    *

    Device trust for BYOD: Enroll devices through Intune (MAM app protection for personal devices, full MDM for corporate-owned). Require compliant or registered devices for access to SAP and the portal. Offer a managed virtual desktop or browser-isolation option for devices that cannot comply.
    *

    Service account clean-up: Assign owners, vault credentials (CyberArk, Entra-integrated vault or AWS Secrets Manager), start rotation, and split shared accounts into per-application identities. Move to gMSAs or managed identities where possible.
    *

    Privileged access: Introduce admin tiering, separate admin accounts, and just-in-time elevation (PIM). Harden the Entra Connect server and treat it as Tier 0.

    • Deploy EDR on all servers and managed endpoints, and start centralizing logs into a SIEM.

    Phase 2: Micro-Segmentation & Policy Enforcement (31-90 Days)

    Segment by business function: Create zones for SAP (app and database tiers), file servers, user endpoints, management/admin, and a quarantine VLAN for unmanaged devices. Begin with

    monitor-only rules based on Phase 1 flow data.
    *

    Replace full-tunnel VPN with ZTNA: Deploy per-application access (Entra Private Access, Zscaler, Cloudflare or similar) for SAP and the file servers. Migrate user groups in waves, keeping the VPN as fallback until each wave is stable.
    *

    Enforce segmentation gradually: Move rules from log-only to enforce one segment at a time. Start with lowest-risk zones, then admin interfaces, then SAP database tier. Use host-based firewalls where VLAN changes are impractical.
    *

    Database access: Route all access through a PAM or bastion layer with named identities, session logging and time-limited credentials; disable direct shared-account logins once applications are migrated.
    *

    Modernize file services: Migrate to Windows Server 2022/2025 or Azure Files/SharePoint with identity-based access, before or alongside the 2016 end-of-support date. Disable SMBv1 and restrict NTLM.
    *

    Protect the AWS portal: Enforce Entra-federated SSO with Conditional Access, tighten security groups and IAM roles to least privilege, and add WAF and logging (CloudTrail, GuardDuty).
    *

    ASA lifecycle: Reduce the ASA to a perimeter role as ZTNA takes over remote access, and plan replacement or upgrade if it is end-of-support.

    Phase 3: Continuous Monitoring & Automation (90+ Days)

    Unified detection: Feed identity, endpoint, network, AWS and SAP logs to the SIEM, with UEBA or anomaly detection for impossible travel, unusual service account use and mass file access.
    *

    Automated response: Build playbooks that isolate non-compliant devices, revoke sessions, disable compromised accounts and trigger credential rotation (SOAR or Defender/Sentinel automation).
    *

    Continuous posture evaluation: Make Conditional Access risk-based, using sign-in risk, device compliance and user risk in real time rather than at login only.
    *

    Access governance: Quarterly access reviews, automated joiner/mover/leaver workflows, and expiring access for privileged roles.
    *

    Validate continuously: Run purple-team exercises and lateral-movement tests against each segment, and track metrics such as percent of apps behind ZTNA, MFA coverage, mean time to contain and number of standing privileged accounts.
    *

    Retire legacy: Decommission VPN access paths, remaining shared accounts and unsupported servers once usage reaches zero.

    3. Business Continuity & Disruption Controls

    Parallel run: Keep the VPN and existing access paths live while ZTNA is rolled out in waves. Cut over a group only after a stable pilot period, and retire old paths only after usage drops to zero.
    *

    Report-only before enforce: Every Conditional Access, firewall and segmentation policy runs in log-only mode first, with a review of what would have been blocked.
    *

    Protect critical systems first: SAP, the support portal and the file servers get change windows outside peak business hours (month-end and quarter-end freeze for SAP), a tested rollback plan, and a named owner for each change.
    *

    Break-glass access: Maintain two emergency Entra admin accounts excluded from Conditional Access, with strong credentials stored offline and alerting on any use. Keep out-of-band console access to the ASAs and servers.
    *

    Backups and rollback: Take verified backups and snapshots (SAP DB, file servers, AWS AMIs/RDS snapshots) before each phase boundary, and export firewall configs before every rule change.
    *

    Service account cutover safety: Introduce new credentials alongside old ones, run both until dependency testing passes, and only then disable the shared account. Do not rotate shared credentials blindly.
    *

    Staged rollout with pilots: IT first, then a low-risk business unit, then everyone else, with a rollback trigger agreed in advance (for example, more than X% access-related tickets).
    *

    Support readiness: Provide a helpdesk runbook, user communication ahead of each wave, and a fast-track channel for blocked access to critical systems.
    *

    Governance: Weekly steering check-ins with business owners of SAP, the portal and file services, and go/no-go criteria at each phase gate.

    I can turn this into a Word document or slide deck for executives, or tailor it further if you share more details such as ASA models, user counts, or SAP version.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Legacy network architectures often rely on perimeter security that fails once a single node is compromised. This skill audits your existing topology to identify lateral movement risks and provides a structured path toward a Zero-Trust Architecture (ZTA).

    What it does

    • Identify vulnerabilities by locating high-risk endpoints and authentication gaps in legacy setups.
    • Phase deployments into logical stages covering identity, micro-segmentation, and monitoring.
    • Protect critical systems by defining fallback mechanisms and parallel run strategies.
    • Map lateral risks to reveal how attackers could move through your current network.

    How it works

    1. Provide topology data including your current network map and critical business systems.
    2. Execute the assessment to generate a threat report focusing on access blind spots.
    3. Review the roadmap which breaks the migration into three distinct time-bound phases.
    4. Implement controls using the provided business continuity strategies to prevent downtime.

    Frameworks & tools

    This skill is designed for environments involving legacy VPNs, on-premise servers, and hybrid cloud setups. It aligns with NIST 800-207 standards for Zero-Trust design.

    Why this beats prompting it yourself

    Generic prompts often miss the operational risks of locking down a live network. this skill enforces a phased timeline and specific disruption controls to ensure you do not crash production services while tightening security.

    Use cases

    • Transitioning a flat corporate network to a micro-segmented environment.
    • Hardening access controls for high-value business systems like ERPs or databases.
    • Creating a multi-month security modernization plan for executive stakeholders.

    Known limitations

    Requires detailed knowledge of existing network assets and critical service dependencies to be effective. It does not perform active network scanning.

    Requires manual input of network topology and critical systems. Does not perform active scanning or automated configuration changes.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 18 days ago

    Permissions

    Read Files
    Write Files
    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill provides a structured, multi-phase migration plan specifically designed to prevent production downtime, unlike generic prompts which may suggest security measures that inadvertently lock out legitimate users.

    The skill aligns with the NIST 800-207 Zero Trust Architecture standards and is optimized for legacy environments involving VPNs, on-premise hardware, and hybrid cloud infrastructures.

    No, the skill performs a static architectural audit based on the topology data you provide; it does not require active network access or perform intrusive scanning, ensuring your current environment remains stable.

    You will receive the full AI agent skill configuration, including the specialized logic for threat mapping and the phased roadmap templates, compatible with major AI orchestration platforms.

    To get the most accurate roadmap, you should be prepared to provide a map of your current network endpoints, identification of high-value business systems, and your existing authentication protocols.

    New in Security