August 5, 2014 at 6:03 am
I had an interesting conversation with one of our security folks yesterday about PowerShell vulnerabilities. He has read several things in the news lately, for example: http://www.securityweek.com/windows-powershell-increasingly-abused-attackers
He inquired if we can remove PowerShell from our environments. Hmmmmm... We standardized on PowerShell for all of our scripts (i.e., database backup, database maintenance, database health checks, etc.) several years ago. So, that would be a complete re-write for us. And, who knows what we would use to replace PowerShell? cmd.exe does not appear to be particularly secure.
A coworker found the following link http://msdn.microsoft.com/en-us/library/ms143506.aspx, which states:
SQL Server 2014 does not install or enable Windows PowerShell 2.0; however Windows PowerShell 2.0 is an installation prerequisite for Database Engine components and SQL Server Management Studio. If Setup reports that Windows PowerShell 2.0 is not present, you can install or enable it by following the instructions on the Windows Management Framework page.
Can anyone share their experiences about PowerShell vulnerabilities and how they address them?
See also old SQL Server Central discussion at http://www.sqlservercentral.com/Forums/Topic941730-1351-1.aspx
August 5, 2014 at 7:02 am
I guess the problem is the age old battle of facility versus abuse. I remember a book on security that specified a secure computer as one with no networking, no ports and in a secure room. Even a keyboard was questionable. Not very useful though.
The problem often appears to be user ignorance (they don't know) or arrogance (they should know better). I have had to recover a family member's computer because they couldn't help themselves but open an attachment because it was so tempting. They knew better. Similar experiences with FaceBook apps too.
PowerShell is too useful and central to remove, however, there is nothing wrong with leaving it locked down. If necessary require changing the execution policy each time a script is run to avoid remote access and privileges.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
August 5, 2014 at 7:23 am
Hmm, oversimplifying, but...
Problem: Someone left the bank vault door unlocked. Robbers took loot & got away in cars.
Solution: Ban cars!
August 5, 2014 at 7:26 am
Gazareth (8/5/2014)
Hmm, oversimplifying, but...Problem: Someone left the bank vault door unlocked. Robbers took loot & got away in cars.
Solution: Ban cars!
...or vaults???
No!!! Banks!!! 😛
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
August 5, 2014 at 8:01 am
Gary Varga (8/5/2014)
Gazareth (8/5/2014)
Hmm, oversimplifying, but...Problem: Someone left the bank vault door unlocked. Robbers took loot & got away in cars.
Solution: Ban cars!
...or vaults???
No!!! Banks!!! 😛
Roads! And bags with dollar signs on them! 🙂
August 5, 2014 at 8:07 am
Gazareth (8/5/2014)
Gary Varga (8/5/2014)
Gazareth (8/5/2014)
Hmm, oversimplifying, but...Problem: Someone left the bank vault door unlocked. Robbers took loot & got away in cars.
Solution: Ban cars!
...or vaults???
No!!! Banks!!! 😛
Roads! And bags with dollar signs on them! 🙂
You win!!! :smooooth:
(Although you ignored internationalization :Whistling:)
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply