summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjvoisin2019-10-22 22:51:59 +0200
committerjvoisin2019-10-22 22:51:59 +0200
commit484eb1b1039df425db46e16569aa68d74b5898b8 (patch)
tree201bebf92a1976f3253768e91f27e260b8463959 /doc
parent6347fa7afa8936ad53c108f15a2ea6ccacd812fb (diff)
Revamp a bit the FAQ
Diffstat (limited to 'doc')
-rw-r--r--doc/source/faq.rst43
1 files changed, 33 insertions, 10 deletions
diff --git a/doc/source/faq.rst b/doc/source/faq.rst
index d8ca973..4974c70 100644
--- a/doc/source/faq.rst
+++ b/doc/source/faq.rst
@@ -41,20 +41,18 @@ Who are you and why did you write Snuffleupagus?
41 41
42We're working for `NBS System <https://nbs-system.com/en/>`__, 42We're working for `NBS System <https://nbs-system.com/en/>`__,
43a web hosting company (meaning that we're dealing with PHP code all day long), 43a web hosting company (meaning that we're dealing with PHP code all day long),
44with a strong focus on security. We do have hardening 44with a strong focus on security. We do have several layers of hardening
45(`kernel <https://grsecurity.net/>`_, `WAF <https://naxsi.org>`_, 45(`kernel <https://grsecurity.net/>`_, `WAF <https://naxsi.org>`_,
46`IDS <https://en.wikipedia.org/wiki/Intrusion_detection_system>`_, etc) 46`IDS <https://en.wikipedia.org/wiki/Intrusion_detection_system>`_, etc),
47below the web stack, but most of the time, when a website is compromised, 47but we had nothing for PHP7.
48it can be to send ads, spam, deface it, steal data etc. 48
49This is why we need to harden the website itself too, but we can't touch its
50source code.
51 49
52Why not Suhosin? 50Why not Suhosin?
53"""""""""""""""" 51""""""""""""""""
54 52
55We're huge fans of `Suhosin <https://suhosin.org>`_, unfortunately: 53We're huge fans of `Suhosin <https://suhosin.org>`_, unfortunately:
56 54
57- it doesn't work very well on PHP 7 55- it doesn't work very well on PHP7
58- it has some oudated features and misses new ones 56- it has some oudated features and misses new ones
59- it doesn't cope very well with our various industrialization needs 57- it doesn't cope very well with our various industrialization needs
60- it has some shortcomings by design 58- it has some shortcomings by design
@@ -65,10 +63,11 @@ the `system <https://secure.php.net/manual/en/function.system.php#refsect1-funct
65function to perform various mandatory maintenance tasks). 63function to perform various mandatory maintenance tasks).
66 64
67This is why we decided to write our own hardening module, in the spirit of Suhosin, 65This is why we decided to write our own hardening module, in the spirit of Suhosin,
68via virtual-patching support, and other cool new features. 66with virtual-patching support, as well as other cool new features.
67
69 68
70What license is Snuffleupagus under and why? 69What license is Snuffleupagus released under and why?
71"""""""""""""""""""""""""""""""""""""""""""" 70"""""""""""""""""""""""""""""""""""""""""""""""""""""
72 71
73Snuffleupagus is licensed under the `LGPL <https://www.gnu.org/copyleft/lesser.html>`_ 72Snuffleupagus is licensed under the `LGPL <https://www.gnu.org/copyleft/lesser.html>`_
74and is developed by the fine people from `NBS System <https://nbs-system.com/>`__. 73and is developed by the fine people from `NBS System <https://nbs-system.com/>`__.
@@ -77,6 +76,18 @@ We chose the LGPL because we don't care that much how you're using Snuffleupagus
77but we'd like to force people to make their improvements/contributions 76but we'd like to force people to make their improvements/contributions
78available to everyone. 77available to everyone.
79 78
79
80What is the different between SNuffleupaugs and a (WAF) like ModSecurity?
81"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
82
83`ModSecurity <https://modsecurity.org/>`__ and the other `Web Application
84Firewall (WAF) <https://en.wikipedia.org/wiki/Web_application_firewall>`__ are
85working by inspecting the http traffic. Snuffleupagus being a PHP module, is
86operating directly inside your website's code, with a lesser overhead, as well
87as a better understanding of what is currently happening inside your
88application.
89
90
80Should I use Snuffleupagus? 91Should I use Snuffleupagus?
81""""""""""""""""""""""""""" 92"""""""""""""""""""""""""""
82 93
@@ -113,6 +124,18 @@ is still a security issue, and should be treated as such.
113We don't have the pretension to state that Snuffleupagus will magically solve 124We don't have the pretension to state that Snuffleupagus will magically solve
114all your security issues, but we believe that it might definitely help. 125all your security issues, but we believe that it might definitely help.
115 126
127
128Sounds great, but is it working?
129""""""""""""""""""""""""""""""""
130
131We've been using it in production since a couple of years, and it thwarted
132numerous known and unknown attacks. If you want some evidences, one of the
133developer published in June 2019 a `blogpost
134<https://dustri.org/b/snuffleupagus-versus-recent-high-profile-vulnerabilities.html>`__
135showcasing how efficient Snuffleupagus was versus *major* web
136vulnerabilities from 2018/2019.
137
138
116Why should I send you bugs, security issues and patches? 139Why should I send you bugs, security issues and patches?
117""""""""""""""""""""""""""""""""""""""""""""""""""""""""" 140"""""""""""""""""""""""""""""""""""""""""""""""""""""""""
118Snuffleupagus is an open-source security software, by reporting (or fixing) 141Snuffleupagus is an open-source security software, by reporting (or fixing)