ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Scripting partioning on AWS

    IT Discussion
    4
    24
    497
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stacksofplatesS
      stacksofplates
      last edited by

      We had to go as far as separating /var/log and /var/log/audit to keep auditd messages separate.

      IRJI 1 Reply Last reply Reply Quote 0
      • IRJI
        IRJ @travisdh1
        last edited by

        @travisdh1 said in Scripting partioning on AWS:

        @IRJ Let's take a step back here. Why are the separate partitions being used?

        A separate /home for a file server makes a lot of sense. Separating out /var and /var/log is a bit odd (unless it's a dedicated rsyslog, greylog, or ELK stack).

        CIS compliance requires it.

        1 Reply Last reply Reply Quote 0
        • IRJI
          IRJ @stacksofplates
          last edited by

          @stacksofplates said in Scripting partioning on AWS:

          We had to go as far as separating /var/log and /var/log/audit to keep auditd messages separate.

          That's level 2. Fortunately I only need level 1 which is still annoying 🙂

          1 Reply Last reply Reply Quote 2
          • IRJI
            IRJ
            last edited by IRJ

            For anyone interested here are the CIS requirements.

            https://secscan.acron.pl/ubuntu1604/1/1/2
            https://secscan.acron.pl/ubuntu1604/1/1/6
            https://secscan.acron.pl/ubuntu1604/1/1/7
            https://secscan.acron.pl/ubuntu1604/1/1/12

            Note: we have Ubuntu 18.04 , but these requirements are the same.

            travisdh1T 2 Replies Last reply Reply Quote 0
            • travisdh1T
              travisdh1 @IRJ
              last edited by

              @IRJ said in Scripting partioning on AWS:

              For anyone interested here are the CIS requirements.

              https://secscan.acron.pl/ubuntu1604/1/1/2
              https://secscan.acron.pl/ubuntu1604/1/1/6
              https://secscan.acron.pl/ubuntu1604/1/1/7
              https://secscan.acron.pl/ubuntu1604/1/1/12

              Note: we have Ubuntu 18.04 , but these requirements are the same.

              Out of the 4 you linked to here, only adding nodev to /tmp even makes sense

              Resizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing, or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations.

              Do they also have you remove LVM and all the tooling for LVM?

              I know, DoD, can't question the system, yadda, yadda. Still doesn't mean I don't call out stupid when I see it.

              stacksofplatesS 1 Reply Last reply Reply Quote 0
              • travisdh1T
                travisdh1 @IRJ
                last edited by

                @IRJ said in Scripting partioning on AWS:

                For anyone interested here are the CIS requirements.

                https://secscan.acron.pl/ubuntu1604/1/1/2
                https://secscan.acron.pl/ubuntu1604/1/1/6
                https://secscan.acron.pl/ubuntu1604/1/1/7
                https://secscan.acron.pl/ubuntu1604/1/1/12

                Note: we have Ubuntu 18.04 , but these requirements are the same.

                Do I recall that you don't have a state management system like Salt or Ansible running correctly? That would be the easiest way to handle this.

                If not, it should also be easy to script this in your favorite shell.

                1 Reply Last reply Reply Quote 0
                • stacksofplatesS
                  stacksofplates @travisdh1
                  last edited by stacksofplates

                  @travisdh1 said in Scripting partioning on AWS:

                  @IRJ said in Scripting partioning on AWS:

                  For anyone interested here are the CIS requirements.

                  https://secscan.acron.pl/ubuntu1604/1/1/2
                  https://secscan.acron.pl/ubuntu1604/1/1/6
                  https://secscan.acron.pl/ubuntu1604/1/1/7
                  https://secscan.acron.pl/ubuntu1604/1/1/12

                  Note: we have Ubuntu 18.04 , but these requirements are the same.

                  Out of the 4 you linked to here, only adding nodev to /tmp even makes sense

                  Resizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing, or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations.

                  I know, DoD, can't question the system, yadda, yadda. Still doesn't mean I don't call out stupid when I see it.

                  I can see value to /var/log. You don't want runaway logs to fill up /. Separating /var and /var/log is much less useful. I can see /home too if it's an interactive system. If not then it's not that useful. Setting nosuid I think is valuable for /tmp also to help ensure something can't be elevated past normal privileges.

                  Do they also have you remove LVM and all the tooling for LVM?

                  We didn't have to for DISA STIGs, that's how we created the volumes.

                  IRJI 1 Reply Last reply Reply Quote 1
                  • IRJI
                    IRJ @stacksofplates
                    last edited by

                    @stacksofplates said in Scripting partioning on AWS:

                    @travisdh1 said in Scripting partioning on AWS:

                    @IRJ said in Scripting partioning on AWS:

                    For anyone interested here are the CIS requirements.

                    https://secscan.acron.pl/ubuntu1604/1/1/2
                    https://secscan.acron.pl/ubuntu1604/1/1/6
                    https://secscan.acron.pl/ubuntu1604/1/1/7
                    https://secscan.acron.pl/ubuntu1604/1/1/12

                    Note: we have Ubuntu 18.04 , but these requirements are the same.

                    Out of the 4 you linked to here, only adding nodev to /tmp even makes sense

                    Resizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing, or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations.

                    I know, DoD, can't question the system, yadda, yadda. Still doesn't mean I don't call out stupid when I see it.

                    I can see value to /var/log. You don't want runaway logs to fill up /. Separating /var and /var/log is much less useful. I can see /home too if it's an interactive system. If not then it's not that useful. Setting nosuid I think is valuable for /tmp also to help insure something can't be elevated past normal privileges.

                    Do they also have you remove LVM and all the tooling for LVM?

                    We didn't have to for DISA STIGs, that's how we created the volumes.

                    Yes we are the same. It seems like we are following the same compliance 🙂

                    stacksofplatesS 1 Reply Last reply Reply Quote 0
                    • stacksofplatesS
                      stacksofplates @IRJ
                      last edited by

                      @IRJ said in Scripting partioning on AWS:

                      @stacksofplates said in Scripting partioning on AWS:

                      @travisdh1 said in Scripting partioning on AWS:

                      @IRJ said in Scripting partioning on AWS:

                      For anyone interested here are the CIS requirements.

                      https://secscan.acron.pl/ubuntu1604/1/1/2
                      https://secscan.acron.pl/ubuntu1604/1/1/6
                      https://secscan.acron.pl/ubuntu1604/1/1/7
                      https://secscan.acron.pl/ubuntu1604/1/1/12

                      Note: we have Ubuntu 18.04 , but these requirements are the same.

                      Out of the 4 you linked to here, only adding nodev to /tmp even makes sense

                      Resizing filesystems is a common activity in cloud-hosted servers. Separate filesystem partitions may prevent successful resizing, or may require the installation of additional tools solely for the purpose of resizing operations. The use of these additional tools may introduce their own security considerations.

                      I know, DoD, can't question the system, yadda, yadda. Still doesn't mean I don't call out stupid when I see it.

                      I can see value to /var/log. You don't want runaway logs to fill up /. Separating /var and /var/log is much less useful. I can see /home too if it's an interactive system. If not then it's not that useful. Setting nosuid I think is valuable for /tmp also to help insure something can't be elevated past normal privileges.

                      Do they also have you remove LVM and all the tooling for LVM?

                      We didn't have to for DISA STIGs, that's how we created the volumes.

                      Yes we are the same. It seems like we are following the same compliance 🙂

                      Used to. Thankfully I'm out of that.

                      1 Reply Last reply Reply Quote 0
                      • IRJI
                        IRJ
                        last edited by IRJ

                        @stacksofplates do you happen to know what sizes were used for the partitions?

                        ObsolesceO stacksofplatesS 2 Replies Last reply Reply Quote 0
                        • IRJI
                          IRJ
                          last edited by

                          Found this chart on a somebody's project on github. Seems like a reasonable place to start?

                          ce0c63ba-39ea-47f3-8720-370ff5d73ff6-image.png

                          stacksofplatesS 1 Reply Last reply Reply Quote 0
                          • ObsolesceO
                            Obsolesce @IRJ
                            last edited by

                            @IRJ said in Scripting partioning on AWS:

                            @stacksofplates do you happen to know what sizes were used for the partitions?

                            How much disk usage is currently in use in those areas?

                            1 Reply Last reply Reply Quote 0
                            • stacksofplatesS
                              stacksofplates @IRJ
                              last edited by

                              @IRJ said in Scripting partioning on AWS:

                              @stacksofplates do you happen to know what sizes were used for the partitions?

                              We didn't do it with a cloud provider. It was internal. I think we usually did 5GB for logs and /var depended on the applications.

                              1 Reply Last reply Reply Quote 0
                              • stacksofplatesS
                                stacksofplates @IRJ
                                last edited by

                                @IRJ said in Scripting partioning on AWS:

                                Found this chart on a somebody's project on github. Seems like a reasonable place to start?

                                ce0c63ba-39ea-47f3-8720-370ff5d73ff6-image.png

                                Ours would have been more like:

                                mount size
                                / 12GB
                                /home 1GB
                                /var 10GB
                                /var/log 5GB
                                /var/log/audit 5GB
                                /tmp 1GB
                                IRJI 1 Reply Last reply Reply Quote 0
                                • IRJI
                                  IRJ @stacksofplates
                                  last edited by

                                  @stacksofplates said in Scripting partioning on AWS:

                                  @IRJ said in Scripting partioning on AWS:

                                  Found this chart on a somebody's project on github. Seems like a reasonable place to start?

                                  ce0c63ba-39ea-47f3-8720-370ff5d73ff6-image.png

                                  Ours would have been more like:

                                  mount size
                                  / 12GB
                                  /home 1GB
                                  /var 10GB
                                  /var/log 5GB
                                  /var/log/audit 5GB
                                  /tmp 1GB

                                  That's a little too liberal for EC2 instances. I could definitely see that working for on prem though.

                                  stacksofplatesS 1 Reply Last reply Reply Quote 0
                                  • stacksofplatesS
                                    stacksofplates @IRJ
                                    last edited by

                                    @IRJ said in Scripting partioning on AWS:

                                    @stacksofplates said in Scripting partioning on AWS:

                                    @IRJ said in Scripting partioning on AWS:

                                    Found this chart on a somebody's project on github. Seems like a reasonable place to start?

                                    ce0c63ba-39ea-47f3-8720-370ff5d73ff6-image.png

                                    Ours would have been more like:

                                    mount size
                                    / 12GB
                                    /home 1GB
                                    /var 10GB
                                    /var/log 5GB
                                    /var/log/audit 5GB
                                    /tmp 1GB

                                    That's a little too liberal for EC2 instances. I could definitely see that working for on prem though.

                                    Yeah. The numbers you had looked fine. Especially if they aren't going to be long living servers.

                                    1 Reply Last reply Reply Quote 3
                                    • 1
                                    • 2
                                    • 1 / 2
                                    • First post
                                      Last post