How to prevent admins to access logs from their own activity?

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
4
down vote

favorite












The idea would be to prevent an attacker who has stolen a root/admin account or escalated to clear its own activities or even read the traces of what he is doing. Let's assume we are under Linux, we log with auditd, and we can use MAC with SELinux. But I am interested also for answers under Windows.



One solution would be to forbid all root accounts to access the logs. Logs are managed only by authorized processes on specific servers from logrotate, syslog, and all SIEM stuff. So only the SOC can read and analyse the admins'logs. Only a purge process can delete old logs. Can one confirm this is doable?



Is it possible to have something more flexible where admins with their own root priviledges could read the logs of other root accounts ?






access-control logging administration







share|improve this question



























    up vote
    4
    down vote

    favorite












    The idea would be to prevent an attacker who has stolen a root/admin account or escalated to clear its own activities or even read the traces of what he is doing. Let's assume we are under Linux, we log with auditd, and we can use MAC with SELinux. But I am interested also for answers under Windows.



    One solution would be to forbid all root accounts to access the logs. Logs are managed only by authorized processes on specific servers from logrotate, syslog, and all SIEM stuff. So only the SOC can read and analyse the admins'logs. Only a purge process can delete old logs. Can one confirm this is doable?



    Is it possible to have something more flexible where admins with their own root priviledges could read the logs of other root accounts ?






    access-control logging administration







    share|improve this question























      up vote
      4
      down vote

      favorite









      up vote
      4
      down vote

      favorite











      The idea would be to prevent an attacker who has stolen a root/admin account or escalated to clear its own activities or even read the traces of what he is doing. Let's assume we are under Linux, we log with auditd, and we can use MAC with SELinux. But I am interested also for answers under Windows.



      One solution would be to forbid all root accounts to access the logs. Logs are managed only by authorized processes on specific servers from logrotate, syslog, and all SIEM stuff. So only the SOC can read and analyse the admins'logs. Only a purge process can delete old logs. Can one confirm this is doable?



      Is it possible to have something more flexible where admins with their own root priviledges could read the logs of other root accounts ?






      access-control logging administration







      share|improve this question













      The idea would be to prevent an attacker who has stolen a root/admin account or escalated to clear its own activities or even read the traces of what he is doing. Let's assume we are under Linux, we log with auditd, and we can use MAC with SELinux. But I am interested also for answers under Windows.



      One solution would be to forbid all root accounts to access the logs. Logs are managed only by authorized processes on specific servers from logrotate, syslog, and all SIEM stuff. So only the SOC can read and analyse the admins'logs. Only a purge process can delete old logs. Can one confirm this is doable?



      Is it possible to have something more flexible where admins with their own root priviledges could read the logs of other root accounts ?






      access-control logging administration




      access-control logging administration






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 hours ago









      lalebarde

      167117




      167117




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          5
          down vote













          The accepted solution to this is to not store the logs locally, but on a log server. Once the logs are there, you can restrict or limit access as you see fit.



          Syslog servers, SIEMs, log aggregators, ELK stacks etc. There are numerous options for you to explore.






          share|improve this answer



























            up vote
            3
            down vote













            Any logs on a compromised host are suspect. You need a centralized logging platform, either a central syslog server/ splunk / logrhythm / whatever. Keep a different set of administrators and accounts. That's the whole idea.



            Once you get a platform in place you can delegate the rights to view their actions, either their own or other admins - can be performed. We had rights read specific log sources and hosts delegated out.






            share|improve this answer




















              Your Answer







              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "162"
              ;
              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: "",
              noCode: true, onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













               

              draft saved


              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f194231%2fhow-to-prevent-admins-to-access-logs-from-their-own-activity%23new-answer', 'question_page');

              );

              Post as a guest

















              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              5
              down vote













              The accepted solution to this is to not store the logs locally, but on a log server. Once the logs are there, you can restrict or limit access as you see fit.



              Syslog servers, SIEMs, log aggregators, ELK stacks etc. There are numerous options for you to explore.






              share|improve this answer
























                up vote
                5
                down vote













                The accepted solution to this is to not store the logs locally, but on a log server. Once the logs are there, you can restrict or limit access as you see fit.



                Syslog servers, SIEMs, log aggregators, ELK stacks etc. There are numerous options for you to explore.






                share|improve this answer






















                  up vote
                  5
                  down vote










                  up vote
                  5
                  down vote









                  The accepted solution to this is to not store the logs locally, but on a log server. Once the logs are there, you can restrict or limit access as you see fit.



                  Syslog servers, SIEMs, log aggregators, ELK stacks etc. There are numerous options for you to explore.






                  share|improve this answer












                  The accepted solution to this is to not store the logs locally, but on a log server. Once the logs are there, you can restrict or limit access as you see fit.



                  Syslog servers, SIEMs, log aggregators, ELK stacks etc. There are numerous options for you to explore.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 2 hours ago









                  schroeder♦

                  64.9k25138175




                  64.9k25138175






















                      up vote
                      3
                      down vote













                      Any logs on a compromised host are suspect. You need a centralized logging platform, either a central syslog server/ splunk / logrhythm / whatever. Keep a different set of administrators and accounts. That's the whole idea.



                      Once you get a platform in place you can delegate the rights to view their actions, either their own or other admins - can be performed. We had rights read specific log sources and hosts delegated out.






                      share|improve this answer
























                        up vote
                        3
                        down vote













                        Any logs on a compromised host are suspect. You need a centralized logging platform, either a central syslog server/ splunk / logrhythm / whatever. Keep a different set of administrators and accounts. That's the whole idea.



                        Once you get a platform in place you can delegate the rights to view their actions, either their own or other admins - can be performed. We had rights read specific log sources and hosts delegated out.






                        share|improve this answer






















                          up vote
                          3
                          down vote










                          up vote
                          3
                          down vote









                          Any logs on a compromised host are suspect. You need a centralized logging platform, either a central syslog server/ splunk / logrhythm / whatever. Keep a different set of administrators and accounts. That's the whole idea.



                          Once you get a platform in place you can delegate the rights to view their actions, either their own or other admins - can be performed. We had rights read specific log sources and hosts delegated out.






                          share|improve this answer












                          Any logs on a compromised host are suspect. You need a centralized logging platform, either a central syslog server/ splunk / logrhythm / whatever. Keep a different set of administrators and accounts. That's the whole idea.



                          Once you get a platform in place you can delegate the rights to view their actions, either their own or other admins - can be performed. We had rights read specific log sources and hosts delegated out.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 2 hours ago









                          Tim Brigham

                          2,80022033




                          2,80022033



























                               

                              draft saved


                              draft discarded















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f194231%2fhow-to-prevent-admins-to-access-logs-from-their-own-activity%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