From: "Sven Vermeulen" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-docs:master commit in: xml/SCAP/
Date: Wed, 26 Mar 2014 21:07:00 +0000 (UTC) [thread overview]
Message-ID: <1395868010.e776b21bb7b10d185eeaebb8a97686a932a3b78c.swift@gentoo> (raw)
commit: e776b21bb7b10d185eeaebb8a97686a932a3b78c
Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Wed Mar 26 21:06:50 2014 +0000
Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org>
CommitDate: Wed Mar 26 21:06:50 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=e776b21b
Add syslog rules and enhance security/access.conf with an example
---
xml/SCAP/gentoo-xccdf.xml | 80 ++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 76 insertions(+), 4 deletions(-)
diff --git a/xml/SCAP/gentoo-xccdf.xml b/xml/SCAP/gentoo-xccdf.xml
index d2bf154..5fe590d 100644
--- a/xml/SCAP/gentoo-xccdf.xml
+++ b/xml/SCAP/gentoo-xccdf.xml
@@ -1,13 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
-<Benchmark xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:h="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.gentoo.dev.swift_benchmark_gentoo-20130917-1" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.2 xccdf-1.2.xsd" resolved="0">
- <status date="2014-02-01">draft</status>
+<Benchmark xmlns="http://checklists.nist.gov/xccdf/1.2" xmlns:h="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="xccdf_org.gentoo.dev.swift_benchmark_gentoo-20140326-1" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.2 xccdf-1.2.xsd" resolved="0">
+ <status date="2014-03-26">draft</status>
<title>Gentoo Security Benchmark</title>
<description>
This benchmarks helps people in improving their system configuration to be
more resilient against attacks and vulnerabilities.
</description>
<platform idref="cpe:/o:gentoo:linux"/>
- <version>20140201.1</version>
+ <version>20140326.1</version>
<model system="urn:xccdf:scoring:default" />
<model system="urn:xccdf:scoring:flat" />
<model system="urn:xccdf:scoring:flat-unweighted" />
@@ -355,7 +355,7 @@
</Group>
</Group>
<Group id="xccdf_org.gentoo.dev.swift_group_preinstallation">
- <title>Before startng</title>
+ <title>Before starting</title>
<description>
Before starting to deploy Gentoo Linux and start hardening it, it is wise
to take a step back and think about what to accomplish. Setting
@@ -1244,6 +1244,48 @@ sed -i -e 's:^rc_shell=.*:rc_shell="/sbin/sulogin":g' /etc/rc.conf
</description>
</Group>
</Group>
+ <Group id="xccdf_org.gentoo.dev.swift_group_system-services-syslog">
+ <title>Syslog service</title>
+ <description>
+ <h:p>
+ The system logger handles all non-audit related logging generated by applications
+ and daemons. In order to ensure proper forensic analysis if it would ever be needed,
+ the system logger should be properly configured.
+ </h:p>
+ </description>
+ <Group id="xccdf_org.gentoo.dev.swift_group_system-services-syslog-logintervals">
+ <title>Configure the system logger to log intervals</title>
+ <description>
+ <h:p>
+ Have the system logger log every 10 minutes or so. Without interval logging,
+ administrators might think nothing is wrong although in reality the system
+ logger is malfunctioning and not writing any log events.
+ </h:p>
+ </description>
+ </Group>
+ <Group id="xccdf_org.gentoo.dev.swift_group_system-services-syslog-remotelogging">
+ <title>Enable remote logging</title>
+ <description>
+ <h:p>
+ If possible, have vital (or all) logs sent to a remote system logger as well.
+ In home deployments, off-the-shelf (wifi) routers often have a logging daemon
+ that can receive syslog events. For larger environments, a dedicated centralized
+ log server is recommended.
+ </h:p>
+ </description>
+ </Group>
+ <Group id="xccdf_org.gentoo.dev.swift_group_system-services-syslog-terminal">
+ <title>Decide which events to send to user terminals</title>
+ <description>
+ <h:p>
+ On Linux and Unix systems, events can be sent to user terminals to
+ make those users immediately aware of what is happening. It is
+ recommended to send emergency-level events to everyone and have
+ alerts sent to specific administrative user terminals.
+ </h:p>
+ </description>
+ </Group>
+ </Group>
</Group>
<Group id="xccdf_org.gentoo.dev.swift_group_system-portage">
<title>Portage settings</title>
@@ -1551,6 +1593,14 @@ tty12</h:pre>
account (say <h:code>apache</h:code>) is abused to log on with, or
that a new account is created as part of an exploit.
</h:p>
+ <h:p>
+ The following example setting allows only local root logins on tty1,
+ and only the <h:em>swift</h:em> account to log on on the system.
+ </h:p>
+ <h:pre>
++ : root : tty1
+- : ALL EXCEPT swift : ALL
+ </h:pre>
</description>
</Group>
<Group id="xccdf_org.gentoo.dev.swift_group_system-auth-resources">
@@ -1731,6 +1781,28 @@ session required pam_unix.so</h:pre>
</h:p>
</description>
</Group>
+ <Group id="xccdf_org.gentoo.dev.swift_group_system-fileprivileges-caps">
+ <title>Limit capability enabled files</title>
+ <description>
+ <h:p>
+ Capabilities within Linux allow users to perform certain privileged tasks.
+ </h:p>
+ <h:p>
+ Unlike <h:em>setuid</h:em> flags, the allowed privileges can be defined
+ in a more granular approach (although one can still add in all possible
+ capabilities and thus gain similar privileges as through <h:em>setuid</h:em>
+ binaries).
+ </h:p>
+ <h:p>
+ Files with particular capabilities set (through the <h:b>setcap</h:b>
+ application) should be regularly reviewed. Capability-enabled files
+ can be found through the following command:
+ </h:p>
+ <h:pre>
+# <h:b>getcap -r /</h:b>
+ </h:pre>
+ </description>
+ </Group>
<Group id="xccdf_org.gentoo.dev.swift_group_system-fileprivileges-logs">
<title>Logs only readable by proper group</title>
<description>
next reply other threads:[~2014-03-26 21:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 21:07 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-04 19:50 [gentoo-commits] proj/hardened-docs:master commit in: xml/SCAP/ Sven Vermeulen
2015-09-02 20:24 Sven Vermeulen
2014-03-30 20:08 Sven Vermeulen
2014-03-30 20:08 Sven Vermeulen
2014-03-30 18:29 Sven Vermeulen
2014-03-30 18:29 Sven Vermeulen
2014-02-01 14:24 Sven Vermeulen
2014-02-01 14:24 Sven Vermeulen
2014-02-01 14:24 Sven Vermeulen
2014-02-01 14:24 Sven Vermeulen
2013-12-20 14:48 Sven Vermeulen
2013-12-20 14:47 Sven Vermeulen
2013-12-20 14:41 Sven Vermeulen
2013-12-20 14:38 Sven Vermeulen
2013-12-20 14:25 Sven Vermeulen
2013-12-20 14:15 Sven Vermeulen
2013-12-20 14:15 Sven Vermeulen
2013-12-20 13:56 Sven Vermeulen
2013-12-20 13:56 Sven Vermeulen
2013-12-20 13:56 Sven Vermeulen
2013-12-20 13:56 Sven Vermeulen
2013-12-20 13:56 Sven Vermeulen
2013-12-20 13:56 Sven Vermeulen
2013-12-20 10:59 Sven Vermeulen
2013-12-11 20:58 Sven Vermeulen
2013-12-11 20:58 Sven Vermeulen
2013-12-11 20:53 Sven Vermeulen
2013-12-11 20:53 Sven Vermeulen
2013-09-24 17:10 Sven Vermeulen
2013-09-23 11:46 Sven Vermeulen
2013-09-23 11:40 Sven Vermeulen
2013-09-19 19:26 Sven Vermeulen
2013-09-18 13:51 Sven Vermeulen
2013-09-17 19:07 Sven Vermeulen
2013-09-17 19:07 Sven Vermeulen
2013-09-17 19:07 Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395868010.e776b21bb7b10d185eeaebb8a97686a932a3b78c.swift@gentoo \
--to=swift@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox