ObSimRef
  • Bedrijf
  • Diensten
  • Ventures
  • Artikelen
    • Het web op het hakblok
    • Windows 2000 IP filtering
    • NetCache C230 Evaluatie
      • Deliverable
      • Part I: Executive Summary
      • Part II: NetCache C230 testreport
        • Getting started
        • Testing the NetApp
        • Functioning within the SURFnet caching mesh
        • NetCache security
          • Installation and Configuration
          • Performance and Stability
          • Conclusions
        • Part III: Appendices
        • Part IV
    • Deze pagina in:
      • English
      • Nederlands
    home | contact
    ObSimRef BV
    Renbaanstraat 2
    7523 ZW Enschede
    tel:+31-53-4280105
    fax:+31-53-4280109
    info@obsimref.com

    NetCache security

     

    5.1 Denial of Service (DoS) Attacks

    The NetApp C230 has been tested against all DoS attacks that are mentioned in the CERT archives (Land, Teardrop, Winnuke et al.). The NetApp is not vulnerable to any of these attacks. As far as we can tell, it is not currently possible to remotely crash a NetApp C230 without administrative permissions. Some attacks, however, might cause some performance degradation. These will only slow down the NetApp, but not interrupt the service in any way.

    5.2 Access

    We found the security features of the NetApp C230 lacking. Only insecure protocols can be used for configuration (telnet, HTTP without SSL). Usage of insecure protocols for administrative access to servers is forbidden according to our site's security policy, and can only be allowed on 'secure' networks.

    We solved this problem by agreeing to never use the telnet access from outside the Computing Center, and connecting the NetApp's console port to a nearby server with SSH.. In a phonecall with NetApp Tech Support, they assured us that there will be SSL capabilities in one of the next software releases.

    Another thing that surprised us was that the NetApp OS is currently running some daemons that can not be turned off or configured at all; it turned out that a RPC portmapper is running. While this doesn't directly affect security, it has absolutely nothing to do with webcaching.

    The rpcinfo output:

    program vers proto port
    100024 1 tcp 610 status
    100024 1 udp 609 status
    100011 1 udp 608 rquotad
    100021 4 tcp 607 nlockmgr
    100021 4 udp 606 nlockmgr
    100021 3 tcp 605 nlockmgr
    100021 3 udp 604 nlockmgr
    100021 1 tcp 603 nlockmgr
    100021 1 udp 602 nlockmgr
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper