<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SD Access DNAC - Hardening in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5203576#M3540</link>
    <description>&lt;P&gt;Hi Akhil,&lt;/P&gt;&lt;P&gt;The following are some points you can consider for Cisco DNA Center (DNAC) to further secure your SD-Access deployment:&lt;/P&gt;&lt;P&gt;1. Role-Based Access Control (RBAC):&lt;BR /&gt;Ensure that users only have the necessary permissions to perform their tasks. Configure appropriate roles for administrators, network operators, and other users.&lt;BR /&gt;Regularly audit user roles and access permissions.&lt;BR /&gt;2. Enable Secure Communication (HTTPS/SSH):&lt;BR /&gt;Ensure all management communication to and from DNAC is encrypted.&lt;BR /&gt;Enforce HTTPS for the DNAC web interface and SSH for CLI access.&lt;BR /&gt;Disable weaker encryption protocols (like HTTP or Telnet) to reduce exposure.&lt;BR /&gt;3. Certificate Management:&lt;BR /&gt;Use valid SSL certificates for the DNAC GUI.&lt;BR /&gt;Consider integrating DNAC with a Certificate Authority (CA) for automatic certificate provisioning and renewal.&lt;BR /&gt;4. Segmentation of Management Traffic:&lt;BR /&gt;Ensure that the management traffic (e.g., between DNAC and the network devices) is isolated using VLANs or dedicated management networks.&lt;BR /&gt;Restrict access to the DNAC management interface from untrusted networks.&lt;BR /&gt;5. IP Whitelisting and ACLs:&lt;BR /&gt;Configure Access Control Lists (ACLs) on upstream network devices to allow only specific IP addresses to communicate with DNAC.&lt;BR /&gt;Restrict access to DNAC based on IP address, ensuring only approved devices and administrators can reach it.&lt;BR /&gt;6. Two-Factor Authentication (2FA):&lt;BR /&gt;Integrate 2FA/Multi-factor authentication (MFA) for DNAC login to enhance security for user accounts.&lt;BR /&gt;7. Software and Patch Management:&lt;BR /&gt;Regularly check for and apply software updates and security patches for DNAC and the underlying infrastructure.&lt;BR /&gt;Automate patch management if possible to avoid gaps in security.&lt;BR /&gt;8. Audit Logs and Monitoring:&lt;BR /&gt;Review audit logs regularly for suspicious activities. Enable full logging capabilities (e.g., login attempts, configuration changes).&lt;BR /&gt;Integrate DNAC logs with a SIEM (Security Information and Event Management) system to monitor and analyze security events.&lt;BR /&gt;9. Disable Unused Services and Ports:&lt;BR /&gt;Identify and disable any unused services or unnecessary ports on DNAC to reduce the attack surface.&lt;BR /&gt;Verify that the only essential ports are open (e.g., for TACACS+, syslog, SSH, HTTPS).&lt;BR /&gt;10. API Security:&lt;BR /&gt;If using the DNAC APIs, ensure that they are secured with proper authentication and access controls.&lt;BR /&gt;Apply rate-limiting to prevent API abuse.&lt;BR /&gt;11. DNAC Identity and Trust Settings:&lt;BR /&gt;Securely configure DNAC trust settings for device onboarding, such as using secure protocols and ensuring that devices are authenticated before accessing the network.&lt;BR /&gt;12. Encrypted Data at Rest:&lt;BR /&gt;Ensure that any sensitive data stored on DNAC is encrypted at rest.&lt;BR /&gt;Consider disk encryption for physical and virtual deployments.&lt;BR /&gt;13. Password Policy Enforcement:&lt;BR /&gt;Enforce a strong password policy for DNAC users and ensure periodic password changes.&lt;BR /&gt;Implement account lockout policies for repeated failed login attempts to prevent brute-force attacks.&lt;BR /&gt;14. Device Hardening and Compliance Checks:&lt;BR /&gt;Use DNAC’s compliance features to ensure that network devices are hardened and meet security standards.&lt;BR /&gt;Regularly check compliance for outdated device configurations, weak passwords, or open security vulnerabilities.&lt;BR /&gt;Implementing these measures will significantly improve the security posture of your Cisco DNAC deployment in SD-Access environments.&lt;/P&gt;</description>
    <pubDate>Fri, 04 Oct 2024 17:20:05 GMT</pubDate>
    <dc:creator>Maher Abdelshkour</dc:creator>
    <dc:date>2024-10-04T17:20:05Z</dc:date>
    <item>
      <title>SD Access DNAC - Hardening</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5203558#M3539</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Recently deployed SD Access. Please suggest what are the hardening points we need to consider for DNAC.&lt;/P&gt;&lt;P&gt;Below points are already completed&lt;/P&gt;&lt;P&gt;1. Tacacs Integration&lt;/P&gt;&lt;P&gt;2. Syslog Configuration&lt;/P&gt;&lt;P&gt;3. NTP&lt;/P&gt;&lt;P&gt;4. Login Banner&lt;/P&gt;&lt;P&gt;5. SNMP Configuration&lt;/P&gt;&lt;P&gt;6. Backup Server Configuration&lt;/P&gt;</description>
      <pubDate>Fri, 04 Oct 2024 17:05:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5203558#M3539</guid>
      <dc:creator>akhil kamalakaran</dc:creator>
      <dc:date>2024-10-04T17:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: SD Access DNAC - Hardening</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5203576#M3540</link>
      <description>&lt;P&gt;Hi Akhil,&lt;/P&gt;&lt;P&gt;The following are some points you can consider for Cisco DNA Center (DNAC) to further secure your SD-Access deployment:&lt;/P&gt;&lt;P&gt;1. Role-Based Access Control (RBAC):&lt;BR /&gt;Ensure that users only have the necessary permissions to perform their tasks. Configure appropriate roles for administrators, network operators, and other users.&lt;BR /&gt;Regularly audit user roles and access permissions.&lt;BR /&gt;2. Enable Secure Communication (HTTPS/SSH):&lt;BR /&gt;Ensure all management communication to and from DNAC is encrypted.&lt;BR /&gt;Enforce HTTPS for the DNAC web interface and SSH for CLI access.&lt;BR /&gt;Disable weaker encryption protocols (like HTTP or Telnet) to reduce exposure.&lt;BR /&gt;3. Certificate Management:&lt;BR /&gt;Use valid SSL certificates for the DNAC GUI.&lt;BR /&gt;Consider integrating DNAC with a Certificate Authority (CA) for automatic certificate provisioning and renewal.&lt;BR /&gt;4. Segmentation of Management Traffic:&lt;BR /&gt;Ensure that the management traffic (e.g., between DNAC and the network devices) is isolated using VLANs or dedicated management networks.&lt;BR /&gt;Restrict access to the DNAC management interface from untrusted networks.&lt;BR /&gt;5. IP Whitelisting and ACLs:&lt;BR /&gt;Configure Access Control Lists (ACLs) on upstream network devices to allow only specific IP addresses to communicate with DNAC.&lt;BR /&gt;Restrict access to DNAC based on IP address, ensuring only approved devices and administrators can reach it.&lt;BR /&gt;6. Two-Factor Authentication (2FA):&lt;BR /&gt;Integrate 2FA/Multi-factor authentication (MFA) for DNAC login to enhance security for user accounts.&lt;BR /&gt;7. Software and Patch Management:&lt;BR /&gt;Regularly check for and apply software updates and security patches for DNAC and the underlying infrastructure.&lt;BR /&gt;Automate patch management if possible to avoid gaps in security.&lt;BR /&gt;8. Audit Logs and Monitoring:&lt;BR /&gt;Review audit logs regularly for suspicious activities. Enable full logging capabilities (e.g., login attempts, configuration changes).&lt;BR /&gt;Integrate DNAC logs with a SIEM (Security Information and Event Management) system to monitor and analyze security events.&lt;BR /&gt;9. Disable Unused Services and Ports:&lt;BR /&gt;Identify and disable any unused services or unnecessary ports on DNAC to reduce the attack surface.&lt;BR /&gt;Verify that the only essential ports are open (e.g., for TACACS+, syslog, SSH, HTTPS).&lt;BR /&gt;10. API Security:&lt;BR /&gt;If using the DNAC APIs, ensure that they are secured with proper authentication and access controls.&lt;BR /&gt;Apply rate-limiting to prevent API abuse.&lt;BR /&gt;11. DNAC Identity and Trust Settings:&lt;BR /&gt;Securely configure DNAC trust settings for device onboarding, such as using secure protocols and ensuring that devices are authenticated before accessing the network.&lt;BR /&gt;12. Encrypted Data at Rest:&lt;BR /&gt;Ensure that any sensitive data stored on DNAC is encrypted at rest.&lt;BR /&gt;Consider disk encryption for physical and virtual deployments.&lt;BR /&gt;13. Password Policy Enforcement:&lt;BR /&gt;Enforce a strong password policy for DNAC users and ensure periodic password changes.&lt;BR /&gt;Implement account lockout policies for repeated failed login attempts to prevent brute-force attacks.&lt;BR /&gt;14. Device Hardening and Compliance Checks:&lt;BR /&gt;Use DNAC’s compliance features to ensure that network devices are hardened and meet security standards.&lt;BR /&gt;Regularly check compliance for outdated device configurations, weak passwords, or open security vulnerabilities.&lt;BR /&gt;Implementing these measures will significantly improve the security posture of your Cisco DNAC deployment in SD-Access environments.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Oct 2024 17:20:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5203576#M3540</guid>
      <dc:creator>Maher Abdelshkour</dc:creator>
      <dc:date>2024-10-04T17:20:05Z</dc:date>
    </item>
    <item>
      <title>Re: SD Access DNAC - Hardening</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5204901#M3549</link>
      <description>&lt;P&gt;Thank you sir, for share the information.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2024 03:25:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-dnac-hardening/m-p/5204901#M3549</guid>
      <dc:creator>akhil kamalakaran</dc:creator>
      <dc:date>2024-10-08T03:25:54Z</dc:date>
    </item>
  </channel>
</rss>

