diff --git a/usbguard-disable-console-log.patch b/usbguard-disable-console-log.patch
new file mode 100644
index 0000000..de88bc1
--- /dev/null
+++ b/usbguard-disable-console-log.patch
@@ -0,0 +1,12 @@
+diff -up usbguard-1.0.0/usbguard.service.in.orig usbguard-1.0.0/usbguard.service.in
+--- usbguard-1.0.0/usbguard.service.in.orig	2023-01-05 13:49:33.830500992 +0100
++++ usbguard-1.0.0/usbguard.service.in	2023-01-05 13:49:41.455507265 +0100
+@@ -8,7 +8,7 @@ OOMScoreAdjust=-1000
+ AmbientCapabilities=
+ CapabilityBoundingSet=CAP_CHOWN CAP_FOWNER CAP_AUDIT_WRITE
+ DevicePolicy=closed
+-ExecStart=%sbindir%/usbguard-daemon -f -s -c %sysconfdir%/usbguard/usbguard-daemon.conf
++ExecStart=%sbindir%/usbguard-daemon -f -s -K -c %sysconfdir%/usbguard/usbguard-daemon.conf
+ IPAddressDeny=any
+ LockPersonality=yes
+ MemoryDenyWriteExecute=yes
diff --git a/usbguard-permanent-rules.patch b/usbguard-permanent-rules.patch
new file mode 100644
index 0000000..845c702
--- /dev/null
+++ b/usbguard-permanent-rules.patch
@@ -0,0 +1,68 @@
+diff -up usbguard-1.0.0/doc/man/usbguard-daemon.conf.5.adoc.orig usbguard-1.0.0/doc/man/usbguard-daemon.conf.5.adoc
+--- usbguard-1.0.0/doc/man/usbguard-daemon.conf.5.adoc.orig	2023-01-05 10:58:24.684407437 +0100
++++ usbguard-1.0.0/doc/man/usbguard-daemon.conf.5.adoc	2023-01-05 10:58:42.323426745 +0100
+@@ -27,7 +27,12 @@ It may be overridden using the *-c* comm
+     behave like any other standard Linux daemon therefore it loads rule files in
+     alpha-numeric order. File names inside `RuleFolder` directory should start
+     with a two-digit number prefix indicating the position, in which the rules
+-    are scanned by the daemon.
++    are scanned by the daemon. Using RuleFile and RuleFolder at the same time is
++    permitted. However, modification of the permanent policy is not possible if
++    one of the following conditions are met:
++    ** Neither RuleFile nor RuleFolder are specified.
++    ** RuleFile is not specified, RuleFolder is but it does not contain any files,
++       where we could save permanent rules.
+ 
+ *ImplicitPolicyTarget*='target'::
+     How to treat USB devices that don't match any rule in the policy. Target
+diff -up usbguard-1.0.0/src/Daemon/Daemon.cpp.orig usbguard-1.0.0/src/Daemon/Daemon.cpp
+--- usbguard-1.0.0/src/Daemon/Daemon.cpp.orig	2023-01-05 10:58:49.689434809 +0100
++++ usbguard-1.0.0/src/Daemon/Daemon.cpp	2023-01-05 10:59:18.991466884 +0100
+@@ -742,7 +742,7 @@ namespace usbguard
+     /* TODO: reevaluate the firewall rules for all active devices */
+     const uint32_t id = _policy.appendRule(rule, parent_id);
+ 
+-    if (_config.hasSettingValue("RuleFile") && permanent) {
++    if ((_config.hasSettingValue("RuleFile") || _config.hasSettingValue("RuleFolder")) && permanent) {
+       _policy.save();
+     }
+ 
+@@ -755,7 +755,7 @@ namespace usbguard
+     USBGUARD_LOG(Trace) << "id=" << id;
+     _policy.removeRule(id);
+ 
+-    if (_config.hasSettingValue("RuleFile")) {
++    if (_config.hasSettingValue("RuleFile") || _config.hasSettingValue("RuleFolder")) {
+       _policy.save();
+     }
+   }
+diff -up usbguard-1.0.0/src/Daemon/RuleSetFactory.cpp.orig usbguard-1.0.0/src/Daemon/RuleSetFactory.cpp
+--- usbguard-1.0.0/src/Daemon/RuleSetFactory.cpp.orig	2023-01-05 10:59:27.117475780 +0100
++++ usbguard-1.0.0/src/Daemon/RuleSetFactory.cpp	2023-01-05 10:59:46.228496702 +0100
+@@ -75,8 +75,24 @@ namespace usbguard
+         }
+       }
+ 
+-      if (ruleSet.empty()){
+-        USBGUARD_LOG(Warning) << "Neither RuleFile nor RuleFolder are set; Modification of the permanent policy won't be possible.";
++      /*
++       * This means one of the following:
++       *  - Neither RuleFile nor RuleFolder are specified
++       *  - RuleFile not specified, RuleFolder is but it does not contain any files,
++       *    where we could save permanent rules
++       */
++      if (ruleSet.empty()) {
++        std::string msg;
++
++        if (ns.getRulesPath().empty() && ns.getRulesDirPath().empty()) {
++          msg = "Neither RuleFile nor RuleFolder are set.";
++        }
++        else {
++          msg = "RuleFile is not set, RuleFolder is but it does not contain any rule files.";
++        }
++
++        USBGUARD_LOG(Warning) << "Modification of the permanent policy won't be possible."
++          << " Reason: " << msg;
+         ruleSet = generateDefaultRuleSet();
+       }
+ 
diff --git a/usbguard.spec b/usbguard.spec
index 2d2eba3..27cac4b 100644
--- a/usbguard.spec
+++ b/usbguard.spec
@@ -8,7 +8,7 @@
 
 Name:           usbguard
 Version:        1.0.0
-Release:        12%{?dist}
+Release:        13%{?dist}
 Summary:        A tool for implementing USB device usage policy
 Group:          System Environment/Daemons
 License:        GPLv2+
@@ -64,6 +64,8 @@ Patch11: usbguard-OOMScoreAdjust.patch
 Patch12: usbguard-daemon-race-condition.patch
 Patch13: usbguard-consistent-rules.patch
 Patch14: usbguard-missing-doc.patch
+Patch15: usbguard-permanent-rules.patch
+Patch16: usbguard-disable-console-log.patch
 
 %description
 The USBGuard software framework helps to protect your computer against rogue USB
@@ -154,6 +156,8 @@ rm -rf src/ThirdParty/{Catch,PEGTL}
 %patch12 -p1 -b .race-condition
 %patch13 -p1 -b .consistent-rules
 %patch14 -p1 -b .missing-doc
+%patch15 -p1 -b .permanent-rules
+%patch16 -p1 -b .disable-console
 
 %build
 mkdir -p ./m4
@@ -318,6 +322,11 @@ fi
 
 
 %changelog
+* Thu Jan 05 2023 Attila Lakatos <alakatos@redhat.com> - 1.0.0-13
+- Disable logging to console, logging to syslog is still enabled
+- Store permanent rules even if RuleFile is not set but RuleFolder is
+Resolves: rhbz#2155910
+
 * Mon Nov 28 2022 Attila Lakatos <alakatos@redhat.com> - 1.0.0-12
 - Set OOMScoreAdjust to -1000 in service file
 Resolves: rhbz#2097419