Guide to protect SQL Server against speculative execution side-channel vulnerabilities





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I am going through this link. My question is regarding Scenario 1 under recommendation as most of our SQL Servers run on physical machine




SQL Server runs on "bare metal" (no virtual machines)



AND no other untrusted application logic (application tier) is run on
the same machine



AND no untrusted SQL Server extensibility interfaces are being used
(see below for list).




What does it mean by untrusted application logic?



Does a webserver running on the same server with internally developed site constitute untrusted application logic?



What about a third party services that monitors the server?










share|improve this question














bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • The definition of "untrusted" is simply up to your judgement. Assuming you trust Microsoft's software, if you trust your web developers and the website is using IIS, then the website is not untrusted. Again, for the monitoring software--do you trust the developer? If it's freeware that you downloaded from www.bobsmalware.com, then probably not, but if it's a major, reputable software developer, then probably.

    – Tony Hinkle
    Jan 8 '18 at 18:12











  • Thanks @TonyHinkle, i was under the impression that the word "Trust" had some technical meaning in programming. Something like the executionpolicy setting in powershell or clr secury.

    – sercurity
    Jan 8 '18 at 19:59











  • @security - now you know, in programming, trusted not secure has no meaning at all :)

    – kakaz
    Jan 10 '18 at 7:56













  • This is probably the most disturbing example of untrusted application logic: en.m.wikipedia.org/wiki/… Notice that antivirus companies was involved in this scam, and AFAIK Symantec was paid for lack of detection. Another example: latest Kaspersky scam.

    – kakaz
    Jan 10 '18 at 8:05


















0















I am going through this link. My question is regarding Scenario 1 under recommendation as most of our SQL Servers run on physical machine




SQL Server runs on "bare metal" (no virtual machines)



AND no other untrusted application logic (application tier) is run on
the same machine



AND no untrusted SQL Server extensibility interfaces are being used
(see below for list).




What does it mean by untrusted application logic?



Does a webserver running on the same server with internally developed site constitute untrusted application logic?



What about a third party services that monitors the server?










share|improve this question














bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • The definition of "untrusted" is simply up to your judgement. Assuming you trust Microsoft's software, if you trust your web developers and the website is using IIS, then the website is not untrusted. Again, for the monitoring software--do you trust the developer? If it's freeware that you downloaded from www.bobsmalware.com, then probably not, but if it's a major, reputable software developer, then probably.

    – Tony Hinkle
    Jan 8 '18 at 18:12











  • Thanks @TonyHinkle, i was under the impression that the word "Trust" had some technical meaning in programming. Something like the executionpolicy setting in powershell or clr secury.

    – sercurity
    Jan 8 '18 at 19:59











  • @security - now you know, in programming, trusted not secure has no meaning at all :)

    – kakaz
    Jan 10 '18 at 7:56













  • This is probably the most disturbing example of untrusted application logic: en.m.wikipedia.org/wiki/… Notice that antivirus companies was involved in this scam, and AFAIK Symantec was paid for lack of detection. Another example: latest Kaspersky scam.

    – kakaz
    Jan 10 '18 at 8:05














0












0








0








I am going through this link. My question is regarding Scenario 1 under recommendation as most of our SQL Servers run on physical machine




SQL Server runs on "bare metal" (no virtual machines)



AND no other untrusted application logic (application tier) is run on
the same machine



AND no untrusted SQL Server extensibility interfaces are being used
(see below for list).




What does it mean by untrusted application logic?



Does a webserver running on the same server with internally developed site constitute untrusted application logic?



What about a third party services that monitors the server?










share|improve this question














I am going through this link. My question is regarding Scenario 1 under recommendation as most of our SQL Servers run on physical machine




SQL Server runs on "bare metal" (no virtual machines)



AND no other untrusted application logic (application tier) is run on
the same machine



AND no untrusted SQL Server extensibility interfaces are being used
(see below for list).




What does it mean by untrusted application logic?



Does a webserver running on the same server with internally developed site constitute untrusted application logic?



What about a third party services that monitors the server?







sql-server sql-server-2014






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 8 '18 at 4:16









sercuritysercurity

434




434





bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • The definition of "untrusted" is simply up to your judgement. Assuming you trust Microsoft's software, if you trust your web developers and the website is using IIS, then the website is not untrusted. Again, for the monitoring software--do you trust the developer? If it's freeware that you downloaded from www.bobsmalware.com, then probably not, but if it's a major, reputable software developer, then probably.

    – Tony Hinkle
    Jan 8 '18 at 18:12











  • Thanks @TonyHinkle, i was under the impression that the word "Trust" had some technical meaning in programming. Something like the executionpolicy setting in powershell or clr secury.

    – sercurity
    Jan 8 '18 at 19:59











  • @security - now you know, in programming, trusted not secure has no meaning at all :)

    – kakaz
    Jan 10 '18 at 7:56













  • This is probably the most disturbing example of untrusted application logic: en.m.wikipedia.org/wiki/… Notice that antivirus companies was involved in this scam, and AFAIK Symantec was paid for lack of detection. Another example: latest Kaspersky scam.

    – kakaz
    Jan 10 '18 at 8:05



















  • The definition of "untrusted" is simply up to your judgement. Assuming you trust Microsoft's software, if you trust your web developers and the website is using IIS, then the website is not untrusted. Again, for the monitoring software--do you trust the developer? If it's freeware that you downloaded from www.bobsmalware.com, then probably not, but if it's a major, reputable software developer, then probably.

    – Tony Hinkle
    Jan 8 '18 at 18:12











  • Thanks @TonyHinkle, i was under the impression that the word "Trust" had some technical meaning in programming. Something like the executionpolicy setting in powershell or clr secury.

    – sercurity
    Jan 8 '18 at 19:59











  • @security - now you know, in programming, trusted not secure has no meaning at all :)

    – kakaz
    Jan 10 '18 at 7:56













  • This is probably the most disturbing example of untrusted application logic: en.m.wikipedia.org/wiki/… Notice that antivirus companies was involved in this scam, and AFAIK Symantec was paid for lack of detection. Another example: latest Kaspersky scam.

    – kakaz
    Jan 10 '18 at 8:05

















The definition of "untrusted" is simply up to your judgement. Assuming you trust Microsoft's software, if you trust your web developers and the website is using IIS, then the website is not untrusted. Again, for the monitoring software--do you trust the developer? If it's freeware that you downloaded from www.bobsmalware.com, then probably not, but if it's a major, reputable software developer, then probably.

– Tony Hinkle
Jan 8 '18 at 18:12





The definition of "untrusted" is simply up to your judgement. Assuming you trust Microsoft's software, if you trust your web developers and the website is using IIS, then the website is not untrusted. Again, for the monitoring software--do you trust the developer? If it's freeware that you downloaded from www.bobsmalware.com, then probably not, but if it's a major, reputable software developer, then probably.

– Tony Hinkle
Jan 8 '18 at 18:12













Thanks @TonyHinkle, i was under the impression that the word "Trust" had some technical meaning in programming. Something like the executionpolicy setting in powershell or clr secury.

– sercurity
Jan 8 '18 at 19:59





Thanks @TonyHinkle, i was under the impression that the word "Trust" had some technical meaning in programming. Something like the executionpolicy setting in powershell or clr secury.

– sercurity
Jan 8 '18 at 19:59













@security - now you know, in programming, trusted not secure has no meaning at all :)

– kakaz
Jan 10 '18 at 7:56







@security - now you know, in programming, trusted not secure has no meaning at all :)

– kakaz
Jan 10 '18 at 7:56















This is probably the most disturbing example of untrusted application logic: en.m.wikipedia.org/wiki/… Notice that antivirus companies was involved in this scam, and AFAIK Symantec was paid for lack of detection. Another example: latest Kaspersky scam.

– kakaz
Jan 10 '18 at 8:05





This is probably the most disturbing example of untrusted application logic: en.m.wikipedia.org/wiki/… Notice that antivirus companies was involved in this scam, and AFAIK Symantec was paid for lack of detection. Another example: latest Kaspersky scam.

– kakaz
Jan 10 '18 at 8:05










1 Answer
1






active

oldest

votes


















0














Untrusted application logic means any application or service running any logic that you(r organization) does not trust.



For your purpose, if you want to be lenient (potentially less secure) you can substitute "unauthorized" for "untrusted" - if the server is running any unauthorized code, it falls under that category.



If you want to be conservative (potentially more secure), assume all your servers run untrusted application logic and move on with that as a founding security assumption, applying the more secure recommendations to them.






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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    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%2f194855%2fguide-to-protect-sql-server-against-speculative-execution-side-channel-vulnerabi%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Untrusted application logic means any application or service running any logic that you(r organization) does not trust.



    For your purpose, if you want to be lenient (potentially less secure) you can substitute "unauthorized" for "untrusted" - if the server is running any unauthorized code, it falls under that category.



    If you want to be conservative (potentially more secure), assume all your servers run untrusted application logic and move on with that as a founding security assumption, applying the more secure recommendations to them.






    share|improve this answer




























      0














      Untrusted application logic means any application or service running any logic that you(r organization) does not trust.



      For your purpose, if you want to be lenient (potentially less secure) you can substitute "unauthorized" for "untrusted" - if the server is running any unauthorized code, it falls under that category.



      If you want to be conservative (potentially more secure), assume all your servers run untrusted application logic and move on with that as a founding security assumption, applying the more secure recommendations to them.






      share|improve this answer


























        0












        0








        0







        Untrusted application logic means any application or service running any logic that you(r organization) does not trust.



        For your purpose, if you want to be lenient (potentially less secure) you can substitute "unauthorized" for "untrusted" - if the server is running any unauthorized code, it falls under that category.



        If you want to be conservative (potentially more secure), assume all your servers run untrusted application logic and move on with that as a founding security assumption, applying the more secure recommendations to them.






        share|improve this answer













        Untrusted application logic means any application or service running any logic that you(r organization) does not trust.



        For your purpose, if you want to be lenient (potentially less secure) you can substitute "unauthorized" for "untrusted" - if the server is running any unauthorized code, it falls under that category.



        If you want to be conservative (potentially more secure), assume all your servers run untrusted application logic and move on with that as a founding security assumption, applying the more secure recommendations to them.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 10 '18 at 2:56









        Anti-weakpasswordsAnti-weakpasswords

        1,464712




        1,464712






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f194855%2fguide-to-protect-sql-server-against-speculative-execution-side-channel-vulnerabi%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            ف. موراي أبراهام

            صرب

            كأس إنترتوتو