cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Level 7
Report Inappropriate Content
Message 1 of 5

ePO apache configuration questions

Jump to solution

We have ePO (5.9.1) installed.

We are working on httpd.conf for V-92511 to make it to comply with SV-102599 for root directory directives.

In https://vaulted.io/library/disa-stigs-srgs/apache_server_24_windows_site_security_technical_implemen... it listed the following directives for r1 and r2

For r1:

Order Deny,Allow

Deny from all

For r2:

Require all denied

 

Questions:

1) To update httpd.conf file, should we use directive(s) only for r2 (i.e. 'Require all denied') or the combination of r1 and r2? I think r2 only should be it but someone said we should use both and no hurt.

2) wha'ts the relationship between the directives of r1 and r2? Are they mutual exclusive or accumulative?

3) How to test if the change affects (or break) the ePO on the system? A detailed step-by-step test/verification guide will be very appreciated.

TIA

1 Solution

Accepted Solutions
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 5 of 5

Re: ePO apache configuration questions

Jump to solution

apache modification may break ePO functionality and support may not be able to help if ePO doesn't work 

View solution in original post

4 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: ePO apache configuration questions

Jump to solution

Any customization in apache will not be supported.

Highlighted
Level 7
Report Inappropriate Content
Message 3 of 5

Re: ePO apache configuration questions

Jump to solution
Thanks, is there any documentation I can refer to for this?
Highlighted
Level 7
Report Inappropriate Content
Message 4 of 5

Re: ePO apache configuration questions

Jump to solution

Also want to know - what does 'not supported' mean?

Is it that you can't change the directive(s) at all (otherwise it will break the functionality), or you can do whatever with the directives, the changes won't take effect (and the functionality still works as before)?

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 5 of 5

Re: ePO apache configuration questions

Jump to solution

apache modification may break ePO functionality and support may not be able to help if ePO doesn't work 

View solution in original post

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community