{
    "id": "8da3d26d-1266-42bc-b376-3c7d5c517f92",
    "name": "Securing Networks with Extended Access Lists",
    "slug": "securing-networks-with-extended-access-lists",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34",
            "4e6a6dc7-e791-4a8e-a598-2acfd5d458c7"
        ],
        "pta_sdn": "368",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-31T17:28:14.953870Z",
    "modified": "2023-10-03T18:58:50.612235Z",
    "is_beta": false,
    "lab_objectives": [],
    "main_learning_area": "e73fd5a8-2ead-4159-9a25-38b50ad4ab20",
    "learning_areas": [
        {
            "id": "e73fd5a8-2ead-4159-9a25-38b50ad4ab20",
            "name": "Networking",
            "slug": "networking"
        }
    ],
    "categories": [],
    "tags": [],
    "difficulty": null,
    "is_web_access": false,
    "is_lab_experience": false,
    "is_featured": false,
    "cve": null,
    "severity": null,
    "year": null,
    "external_url": "",
    "solution_video": "28f05d0a-9ec3-4201-80b2-e8ecf46a8340",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4298/diagram.png)\n\n\n**Helpful Hints about INE\u2019s virtual lab environment:**\n\n- Most INE Networking Labs will timeout after 55-minutes (unless otherwise specified). If you haven't completed a lab within 45-minutes, save your configurations to an external text editor, restart the lab, and then paste in your saved configs to resume where you left off.\n- To access the CLI (command line interface) of any node, right-click that node and select the \"**console**\" option.\n- Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity\n- If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, \u201cAnother GNS3 instance is running, continue? (Y/N)\u201d.  Select \u201cYes\u201d\n- If you ever lose console access to one (or more) of your devices you will need to reboot the Ubuntu Virtual Machine that is hosting your GNS3 lab environment.  To do this,\n    - Minimize your GNS3 window\n    - Open the \u201cTerminal\u201d app within the Ubuntu device\n\n    ![description](https://assets.ine.com/content/labs/networking-labs/Lab-4298/terminal.png)\n\n    - Type \u201creboot\u201d within the Terminal window\n    - Wait 20-30 seconds and then click the \u201cReconnect\u201d option to log back in.",
    "description_html": "<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Lab-4298/diagram.png\" /></p>\n<p><strong>Helpful Hints about INE\u2019s virtual lab environment:</strong></p>\n<ul>\n<li>Most INE Networking Labs will timeout after 55-minutes (unless otherwise specified). If you haven't completed a lab within 45-minutes, save your configurations to an external text editor, restart the lab, and then paste in your saved configs to resume where you left off.</li>\n<li>To access the CLI (command line interface) of any node, right-click that node and select the \"<strong>console</strong>\" option.</li>\n<li>Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity</li>\n<li>If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, \u201cAnother GNS3 instance is running, continue? (Y/N)\u201d.  Select \u201cYes\u201d</li>\n<li>\n<p>If you ever lose console access to one (or more) of your devices you will need to reboot the Ubuntu Virtual Machine that is hosting your GNS3 lab environment.  To do this,</p>\n<ul>\n<li>Minimize your GNS3 window</li>\n<li>Open the \u201cTerminal\u201d app within the Ubuntu device</li>\n</ul>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Lab-4298/terminal.png\" /></p>\n<ul>\n<li>Type \u201creboot\u201d within the Terminal window</li>\n<li>Wait 20-30 seconds and then click the \u201cReconnect\u201d option to log back in.</li>\n</ul>\n</li>\n</ul>",
    "tasks": "**Task: Securing Networks with Extended Access Control Lists**\n\n***NOTE:*** The enable password on all IOS devices is \"**INE**\"\n\n\n1. Login to routers R3 and R4 and confirm that, from both of these routers, you can:\n\n    - Establish an SSH session to router R2 (ssh credentials are **admin/ine**)\n    - Telnet to router R1 (**password=cisco**).\n    - Ping R1, R2 and PC1\n\n2. Configure one or more **named, extended** Access Control Lists and apply it to **only one device in your topology** in such a way that it meets the following criteria:\n\n    - The ACL may not reference any TCP or UDP protocols by name. You must use TCP/UDP port numbers.\n    - Prevents PC4 from pinging PC1 (remember that these two PCs utilize DHCP)\n    - Prevents R3 from establishing an SSH session with R2\n    - Prevents R3 and R4 from establishing a Telnet session with R1 (sourced from the subnet shared by R3 and R4).\n    - Prevents PC1 from resolving any DNS lookups from a hidden DNS server in OSPF Area-51.\n    - This ACL should permit all other IP-based traffic from any source to any destination.\n    - You may use your own discretion setting any parameters required by the ACL that are not mentioned above.\n\n3. Verify that your ACL configuration and application is working per the requirements above (with the exception of testing DNS, which you cannot do in this lab).\n\n\n4. Login to router R1 and you'll notice that there is an existing access control list configured in this router. Edit this list such that:\n\n    - Any lines that deny DNS traffic are removed from the ACL\n    - Any lines that would permit TFTP traffic from 70.70.0.18 or 70.70.0.34 are removed\n    - A new line is inserted permitted Telnet traffic from host 3.3.3.3 to anyone and this line must be inserted in between the existing two ACEs that reference Telnet.\n    - You are NOT allowed to delete this ACL in its entirety and rewrite it. Any action taken on your part **MUST** preserve all other lines of this ACl that are not intentionally removed.",
    "tasks_html": "<p><strong>Task: Securing Networks with Extended Access Control Lists</strong></p>\n<p><strong><em>NOTE:</em></strong> The enable password on all IOS devices is \"<strong>INE</strong>\"</p>\n<ol>\n<li>\n<p>Login to routers R3 and R4 and confirm that, from both of these routers, you can:</p>\n<ul>\n<li>Establish an SSH session to router R2 (ssh credentials are <strong>admin/ine</strong>)</li>\n<li>Telnet to router R1 (<strong>password=cisco</strong>).</li>\n<li>Ping R1, R2 and PC1</li>\n</ul>\n</li>\n<li>\n<p>Configure one or more <strong>named, extended</strong> Access Control Lists and apply it to <strong>only one device in your topology</strong> in such a way that it meets the following criteria:</p>\n<ul>\n<li>The ACL may not reference any TCP or UDP protocols by name. You must use TCP/UDP port numbers.</li>\n<li>Prevents PC4 from pinging PC1 (remember that these two PCs utilize DHCP)</li>\n<li>Prevents R3 from establishing an SSH session with R2</li>\n<li>Prevents R3 and R4 from establishing a Telnet session with R1 (sourced from the subnet shared by R3 and R4).</li>\n<li>Prevents PC1 from resolving any DNS lookups from a hidden DNS server in OSPF Area-51.</li>\n<li>This ACL should permit all other IP-based traffic from any source to any destination.</li>\n<li>You may use your own discretion setting any parameters required by the ACL that are not mentioned above.</li>\n</ul>\n</li>\n<li>\n<p>Verify that your ACL configuration and application is working per the requirements above (with the exception of testing DNS, which you cannot do in this lab).</p>\n</li>\n<li>\n<p>Login to router R1 and you'll notice that there is an existing access control list configured in this router. Edit this list such that:</p>\n<ul>\n<li>Any lines that deny DNS traffic are removed from the ACL</li>\n<li>Any lines that would permit TFTP traffic from 70.70.0.18 or 70.70.0.34 are removed</li>\n<li>A new line is inserted permitted Telnet traffic from host 3.3.3.3 to anyone and this line must be inserted in between the existing two ACEs that reference Telnet.</li>\n<li>You are NOT allowed to delete this ACL in its entirety and rewrite it. Any action taken on your part <strong>MUST</strong> preserve all other lines of this ACl that are not intentionally removed.</li>\n</ul>\n</li>\n</ol>",
    "published_date": "2022-11-01T13:57:33Z",
    "solutions": "***SOLUTIONS***\n\nView the Solution Video accompanying this lab for the lab solutions and walkthrough.",
    "solutions_html": "<p><strong><em>SOLUTIONS</em></strong></p>\n<p>View the Solution Video accompanying this lab for the lab solutions and walkthrough.</p>",
    "flags": [],
    "min_points_to_pass": null,
    "access_type": "default",
    "user_status": "unstarted",
    "user_lab_status": null,
    "user_status_modified": null,
    "user_flags": [],
    "global_running_session": null
}