Is it still best practice to avoid using the default ports for SQL Server?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
2
down vote

favorite












Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice. On a server with a single, default instance, the following ports would be used by default:



  • SQL Server service - Port 1433 (TCP)

  • SQL Server Browser service - Port 1434 (UDP)

  • Dedicated Admin Connection - Port 1434 (TCP)

QUESTIONS:



  • Is this advice still relevant?

  • Should ALL of the above ports be changed?





sql-server security best-practices dynamic-ports







share|improve this question























  • Maybe this post can help you dba.stackexchange.com/questions/213810/…
    – Eleonora Grigoryan
    19 mins ago






  • 1




    I think it is still recognised as a good idea, but the reality is this just slows down an attack more than prevents it. A port scanner is quickly going to find the ones it needs. Changing the port simply disassociates the application with that default port number, which means any hacker needs to do a little more work to figure out which application is listening on any port.
    – DimUser
    19 mins ago

















up vote
2
down vote

favorite












Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice. On a server with a single, default instance, the following ports would be used by default:



  • SQL Server service - Port 1433 (TCP)

  • SQL Server Browser service - Port 1434 (UDP)

  • Dedicated Admin Connection - Port 1434 (TCP)

QUESTIONS:



  • Is this advice still relevant?

  • Should ALL of the above ports be changed?





sql-server security best-practices dynamic-ports







share|improve this question























  • Maybe this post can help you dba.stackexchange.com/questions/213810/…
    – Eleonora Grigoryan
    19 mins ago






  • 1




    I think it is still recognised as a good idea, but the reality is this just slows down an attack more than prevents it. A port scanner is quickly going to find the ones it needs. Changing the port simply disassociates the application with that default port number, which means any hacker needs to do a little more work to figure out which application is listening on any port.
    – DimUser
    19 mins ago













up vote
2
down vote

favorite









up vote
2
down vote

favorite











Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice. On a server with a single, default instance, the following ports would be used by default:



  • SQL Server service - Port 1433 (TCP)

  • SQL Server Browser service - Port 1434 (UDP)

  • Dedicated Admin Connection - Port 1434 (TCP)

QUESTIONS:



  • Is this advice still relevant?

  • Should ALL of the above ports be changed?





sql-server security best-practices dynamic-ports







share|improve this question















Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice. On a server with a single, default instance, the following ports would be used by default:



  • SQL Server service - Port 1433 (TCP)

  • SQL Server Browser service - Port 1434 (UDP)

  • Dedicated Admin Connection - Port 1434 (TCP)

QUESTIONS:



  • Is this advice still relevant?

  • Should ALL of the above ports be changed?





sql-server security best-practices dynamic-ports




sql-server security best-practices dynamic-ports






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 24 mins ago









MDCCL

6,36731740




6,36731740










asked 26 mins ago









James D

404




404











  • Maybe this post can help you dba.stackexchange.com/questions/213810/…
    – Eleonora Grigoryan
    19 mins ago






  • 1




    I think it is still recognised as a good idea, but the reality is this just slows down an attack more than prevents it. A port scanner is quickly going to find the ones it needs. Changing the port simply disassociates the application with that default port number, which means any hacker needs to do a little more work to figure out which application is listening on any port.
    – DimUser
    19 mins ago

















  • Maybe this post can help you dba.stackexchange.com/questions/213810/…
    – Eleonora Grigoryan
    19 mins ago






  • 1




    I think it is still recognised as a good idea, but the reality is this just slows down an attack more than prevents it. A port scanner is quickly going to find the ones it needs. Changing the port simply disassociates the application with that default port number, which means any hacker needs to do a little more work to figure out which application is listening on any port.
    – DimUser
    19 mins ago
















Maybe this post can help you dba.stackexchange.com/questions/213810/…
– Eleonora Grigoryan
19 mins ago




Maybe this post can help you dba.stackexchange.com/questions/213810/…
– Eleonora Grigoryan
19 mins ago




1




1




I think it is still recognised as a good idea, but the reality is this just slows down an attack more than prevents it. A port scanner is quickly going to find the ones it needs. Changing the port simply disassociates the application with that default port number, which means any hacker needs to do a little more work to figure out which application is listening on any port.
– DimUser
19 mins ago





I think it is still recognised as a good idea, but the reality is this just slows down an attack more than prevents it. A port scanner is quickly going to find the ones it needs. Changing the port simply disassociates the application with that default port number, which means any hacker needs to do a little more work to figure out which application is listening on any port.
– DimUser
19 mins ago











1 Answer
1






active

oldest

votes

















up vote
6
down vote














Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice.




Which was asinine then and still asinine now. Security through arguably obscurity isn't security at all.




Is this advice still relevant




IMHO it was never relevant. It was required for some compliance purposes because the people drafting up those compliances did not understand what they were doing, again, IMHO.




Should ALL of the above ports be changed?




I wouldn't change any.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "182"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f220270%2fis-it-still-best-practice-to-avoid-using-the-default-ports-for-sql-server%23new-answer', 'question_page');

    );

    Post as a guest

















    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    6
    down vote














    Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice.




    Which was asinine then and still asinine now. Security through arguably obscurity isn't security at all.




    Is this advice still relevant




    IMHO it was never relevant. It was required for some compliance purposes because the people drafting up those compliances did not understand what they were doing, again, IMHO.




    Should ALL of the above ports be changed?




    I wouldn't change any.






    share|improve this answer
























      up vote
      6
      down vote














      Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice.




      Which was asinine then and still asinine now. Security through arguably obscurity isn't security at all.




      Is this advice still relevant




      IMHO it was never relevant. It was required for some compliance purposes because the people drafting up those compliances did not understand what they were doing, again, IMHO.




      Should ALL of the above ports be changed?




      I wouldn't change any.






      share|improve this answer






















        up vote
        6
        down vote










        up vote
        6
        down vote










        Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice.




        Which was asinine then and still asinine now. Security through arguably obscurity isn't security at all.




        Is this advice still relevant




        IMHO it was never relevant. It was required for some compliance purposes because the people drafting up those compliances did not understand what they were doing, again, IMHO.




        Should ALL of the above ports be changed?




        I wouldn't change any.






        share|improve this answer













        Historically, it has been recommended not to use the default ports for connections to SQL Server, as part of security best practice.




        Which was asinine then and still asinine now. Security through arguably obscurity isn't security at all.




        Is this advice still relevant




        IMHO it was never relevant. It was required for some compliance purposes because the people drafting up those compliances did not understand what they were doing, again, IMHO.




        Should ALL of the above ports be changed?




        I wouldn't change any.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 19 mins ago









        Sean Gallardy

        13.7k11944




        13.7k11944



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f220270%2fis-it-still-best-practice-to-avoid-using-the-default-ports-for-sql-server%23new-answer', 'question_page');

            );

            Post as a guest
































































            Comments

            Post a Comment

            Popular posts from this blog

            Long meetings (6-7 hours a day): Being “babysat” by supervisor

            Image
            Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 31 down vote favorite 4 I hold a PhD in mechanical engineering with a 7 year background in self-guided, self-paced research including 2 years as a graduate level course instructor and a subject matter expert for various engineering projects in a university setting in the United States. For the last 10-11 months, I am working in a research industry in France where my task is to debug C++ spaghetti code written over a period of several years by my current supervisor. It is a team of 2: just I and my supervisor. Diurnally, I am posed with a "bug of the day" to get out of this C++ code. My supervisor generally gives me about 15-30 minutes to solve it and then accosts me about whether or not the task is completed and then rinses and repeats this until the end of the day. Off-late, my supervisor has been holding 6-7 hour long "meetin
            Read more

            Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Many fantasy worlds have multiple humanoid species (elves, orcs, humans, etc) living in the same world, in addition to that, they often have the ability to interbreed. And I can't help but question their believability... fantasy-races reproduction interspecies-relations share | improve this question edited Aug 9 at 14:46 Michael Kjörling ♦ 21.1k 10 85 161 asked Aug 9 at 13:13 Chlodio 118 6 closed as unclear what you're asking by MichaelK, Gryphon, John, Vincent, Frostfyre Aug 9 at 15:25 Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question. 3 Stack Exchange exist to
            Read more

            Confectionery

            Image
            Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of
            Read more