• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 166
  • Last Modified:

Linux VM hardenings : any concern

If we perform the following 3 hardenings for our tenant/customer Linux VM,
will it affect any sysadmin operation (say if password is forgotten, can't recover
back the VM or we can help apply patches for the tenant) and break any apps ?
 

CIS 1.5.3 Set Boot Loader Password
No boot loader password set. Can we set boot loader password and any concern ?

 

CIS 1.5.4 Require Authentication for Single-User Mode
No single-user mode password set. Can we set password protection when boot to single user mode and any concern ?

 

CIS 1.5.5 Disable Interactive Boot
Interactive Boot is enabled. Any concern to disable interactive boot ?
0
sunhux
Asked:
sunhux
  • 6
  • 6
4 Solutions
 
gheistCommented:
No, just that it is a pain to run to office to enter boot passwords mid Xmas holiday....
0
 
sunhuxAuthor Commented:
But the tenant can't access our vCenter so wouldn't that make any
difference if we set the password?  

As far as I know the access of console via vCenter is only
restricted to us, the cloud provider only
0
 
gheistCommented:
Then it makes even less sense... You will get virtual machines that dont boot by themselves, and you need to enter password on them. (Probably possible if you have 10 VMs, but when it gets to 100 you get crazy half way...
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
sunhuxAuthor Commented:
So we (the cloud provider) has to advise the tenants not to set
passwords, else whenever the VM reboots, someone at our (the
cloud provider) end needs to be around to enter the console
password(s) at vCenter, right?
0
 
sunhuxAuthor Commented:
Among the 3, which ones would you recommend not to set password
so as not to cause this inconvenience whenever a VM reboots, it will
not boot up by itself unless the password(s) is entered?
0
 
sunhuxAuthor Commented:
More specifically, I need clarifications on:

a) Set Boot Loader Password:
    if this password is set, when tenant reboot (shutdown -r)
    their VM each time, will it prompt for the bootloader
    password at console?  If so, is there any way the tenant,
    could still get their VM booted up if they have no access
    to vCenter's console?

b) Require Authentication for Single-User Mode
    Does Linux allow ssh access while in single-user mode &
    can this 'single-user mode password' be entered via an
    ssh session (without access to console), assuming certain
    'terminal' service is started up / running while in single
    user mode

c) Disable Interactive Boot:
    what's the general consensus on this? Disable or enable?
    Our corporate hardening guide does not mention this item.
    So if the tenant wishes to boot up step by step (ie pausing
    at each startup script), they can't do it?

Pls add on any other operational impact if the above 3 items
are hardened.
0
 
gheistCommented:
It is meant to protect physical access. With you entering passwords... there is almost no purpose. If your custometr has formal requirement for something that should be applied to protecting your infrastructure and by extension protecting theirs...
0
 
sunhuxAuthor Commented:
For item (b), is there any possibility of getting the network services
& sshd started at runlevel 1 (ie single user mode)?  Any other
services need to be started to be able to ssh in to the VM while
in single-user mode & to be able to enter the password prompted
when prompted to enter at runlevel 1?
0
 
gheistCommented:
b) those services are started AFTER password is entered...
0
 
gheistCommented:
PS loudest attacks of modern times like heartbleed just dumped apache's memory space and all raw host keys, protecting boot loader was irrelevant.
0
 
sunhuxAuthor Commented:
Can you reply directly / specifically to the earlier 3 questions:

 I need clarifications on:

a) Set Boot Loader Password:
    if this password is set, when tenant reboot (shutdown -r)
    their VM each time, will it prompt for the bootloader
    password at console?  If so, is there any way the tenant,
    could still get their VM booted up if they have no access
    to vCenter's console?

b) Require Authentication for Single-User Mode
    Does Linux allow ssh access while in single-user mode &
    can this 'single-user mode password' be entered via an
    ssh session (without access to console), assuming certain
    'terminal' service is started up / running while in single
    user mode

c) Disable Interactive Boot:
    what's the general consensus on this? Disable or enable?
    Our corporate hardening guide does not mention this item.
    So if the tenant wishes to boot up step by step (ie pausing
    at each startup script), they can't do it?

Pls add on any other operational impact if the above 3 items
are hardened.
0
 
gheistCommented:
None of them is relevant to physically securing virtual machine.
Outer virtualisation product has to be secured instead.

assuming attacker gets to VM's management interfaces (more or less equivalent getting to physical machine) he can bypass named protections:
a) by booting off his own livecd
b) by modifying inittab
c) once in single mode one can start stop single service as they choose
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now