<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-03-13 12:47 GMT+01:00 Jan Lieskovsky <span dir="ltr"><<a href="mailto:jlieskov@redhat.com" target="_blank">jlieskov@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">> There are many known tips and tricks how to make a system more secure, often<br>
> depending on the use case for the system. With the OSCAP Anaconda Addon [1]<br>
> and the SCAP Security Guide [2] projects, we may allow users choosing a<br>
> security policy for their newly installed system.<br>
><br>
> What is the proposed default configuration/policy?<br>
<br>
</div>FWIW WRT to scap-security-guide content there's only one (common) profile<br>
at the moment. But it depends on the target group / volume / spin we would like<br>
this to be by default part of -- once this is clear in that case the profile can<br>
be adjusted / modified to prefer / select by default just rules intended for the<br>
target group of that system<br></blockquote></div><br></div><div class="gmail_extra">So, let me be more specific: If I install using the most default setup possible (not touching the policy spoke), will the installed system be affected by the policy / different from what is packaged in the RPMs?<br>
</div><div class="gmail_extra"> Mirek<br></div></div>