- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Securing HP SWS Apache to DoD DISA STIG
Operating System - OpenVMS
1753559
Members
5599
Online
108796
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 09:30 AM
тАО02-17-2011 09:30 AM
Re: Securing HP SWS Apache to DoD DISA STIG
Just reread the question. That depends on the privileges that the webservice is granted.
If the webservice has the privilege to modify system files then yes it is a concern.
So the answer is not to grant that kind of privilege to a webservice, and indeed why would one?
If the webservice has the privilege to modify system files then yes it is a concern.
So the answer is not to grant that kind of privilege to a webservice, and indeed why would one?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 10:03 AM
тАО02-17-2011 10:03 AM
Re: Securing HP SWS Apache to DoD DISA STIG
Most security audits will fail the versions of Apache and php packages available for OpenVMS, among other common tools. (I've worked with auditors that have flagged and failed far newer versions than what are available with VMS.)
The web server should not own and should have extremely limited write access to any device and directory and file resources. The default should be no write access, and no control access, and often a top-level ACL on everything else blocking access. Some web-facing systems do require writeable directories (for client file uploads, usually), and those can be, well, hazardous.
It can be easier to deploy a locked down web server (often in a DMZ) than to try to lock down an existing and active server, too.
Web server attacks now tend to target the injection of php code or of SQL, depending on what services are active and what the site is serving up. Proper file protections are a reasonable backstop for some of that, but are far from a panacea. Other attacks can include gifar uploads (into directories that are writeable) and the recent spate of "fun" that has been Firesheep.
The web server should not own and should have extremely limited write access to any device and directory and file resources. The default should be no write access, and no control access, and often a top-level ACL on everything else blocking access. Some web-facing systems do require writeable directories (for client file uploads, usually), and those can be, well, hazardous.
It can be easier to deploy a locked down web server (often in a DMZ) than to try to lock down an existing and active server, too.
Web server attacks now tend to target the injection of php code or of SQL, depending on what services are active and what the site is serving up. Proper file protections are a reasonable backstop for some of that, but are far from a panacea. Other attacks can include gifar uploads (into directories that are writeable) and the recent spate of "fun" that has been Firesheep.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-17-2011 10:18 AM
тАО02-17-2011 10:18 AM
Re: Securing HP SWS Apache to DoD DISA STIG
Here is the security of HTTPD for HP SWS on OpenVMS.
HTTPD.CONF;15
[AP_HTTPD,APACHE$WWW] (RWED,RWED,,) (IDENTIFIER=APACHE$READ,ACCESS=READ)
So APACHE$WWW owns the file. It has owner access of RWED and the APACHE$READ identifer.
So it looks like the Webservice process that runs as the APACHE$WWW user has write access to the HTTPD.CONF file, unless I'm missing something.
HTTPD.CONF;15
[AP_HTTPD,APACHE$WWW] (RWED,RWED,,) (IDENTIFIER=APACHE$READ,ACCESS=READ)
So APACHE$WWW owns the file. It has owner access of RWED and the APACHE$READ identifer.
So it looks like the Webservice process that runs as the APACHE$WWW user has write access to the HTTPD.CONF file, unless I'm missing something.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-18-2011 02:00 AM
тАО02-18-2011 02:00 AM
Re: Securing HP SWS Apache to DoD DISA STIG
It seems that O:RWED is the standard setting.
I think that the owner should have no access by protection setting.
Interested to know the HP response.
I think that the owner should have no access by protection setting.
Interested to know the HP response.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP