Debian Security Announcements
Since Kicksecure ™ is based on Debian, it takes advantage of all the hard work done by their security team: 
Debian takes security very seriously. We handle all security problems brought to our attention and ensure that they are corrected within a reasonable timeframe. Many advisories are coordinated with other free software vendors and are published the same day a vulnerability is made public and we also have a Security Audit team that reviews the archive looking for new or unfixed security bugs. Experience has shown that "security through obscurity" does not work. Public disclosure allows for more rapid and better solutions to security problems. In that vein, this page addresses Debian's status with respect to various known security holes, which could potentially affect Debian.
Users should consider subscribing to the Debian security announcement mailing list to stay informed about the latest security advisories.
Most hardening steps cannot be easily added to Kicksecure ™ by default. Any major changes require careful research and significant developer/tester effort, otherwise system errors or breakage may occur. This is an open topic and Kicksecure ™ developers are amenable to suggestions - improving operating system security will always be a primary design goal.
Before attempting additional hardening measures below, be sure to fully understand them and apply the steps carefully:
- Debian Hardening Walkthrough
- Debian Security Information
- Securing Debian Manual
Readers are welcome to add any additional hardening resources to this list.
The upstream Kernel Self Protection Project (KSPP)  was established in 2015 with the goal of introducing more hardening features into mainline Linux. This includes many features found in the Grsecurity patchset, which was publicly available until early 2017. One advantage of KSPP is that users will no longer need to compile and tweak settings to create a secure kernel. Instead, many hardening features will become the default over time in various distributions. Up-to-date information on available hardening features can be viewed here.
The Hardened Kernel Project is a collaborative effort between Arch and Gentoo developers who handled Grsecurity packaging in their respective distributions with the goal of accelerating mainlining of the patchset.  
While kernel hardening is important, it only addresses a subset of security risks. It cannot protect against backdoors or security issues related to design, policy or yet unknown exploit classes.
Restricting module loading can protect the kernel.
Chapter "Module Loading" is for advanced users only since it could break various things. This is still under development. See Kicksecure ™ development discussion: allow loading signed kernel modules by default / disallow kernel module loading by default
Kicksecure ™ only:
Disable module loading by creating this file:
After reboot, test if module loading is really disabled. Try to load any module, for example
modprobe: ERROR: could not insert 'apanel': Operation not permitted
Harden Software Repositories
Many operating systems provide multiple repositories. Since the Kicksecure ™ implementation is based on Debian, these resources provide a suitable introduction for interested readers:
In summary, these resources confirm the main repository receives the most developer attention and security updates. This suggests a degree of hardening might involve editing /etc/apt/sources.list to strictly limit software to the main repository, while only installing security fixes and no other updates.
Kicksecure ™ has not implemented this design by default and it is an open research question whether this will actually improve security.
Vulnerabilities at Install Time
Various installation media expose users to vulnerabilities, including:
- Importable VM images: Kicksecure ™ and other images.
- Installer DVDs: Debian and other major platforms.
- Live DVDs: Tails and similar platforms.
- VM Images built with frozen sources: Platforms without current sources.
The threat arises because the latest stable releases sometimes contain vulnerable, remotely exploitable applications. These applications are very likely to be used over untrusted networks  which are in a position to run Man-in-the-Middle Attacks.
One recent example is the January, 2019 APT vulnerability (CVE-2019-3462) which allowed content injection by a MiTM attacker, thereby enabling remote code execution on the affected Linux machine. Specifically, improper sanitization of parameters in HTTP redirects allowed malicious content (altered packages) to be installed via a harmful mirror or direct injection into the network traffic.  For another example, see CVE-2014-6273 which affected APT in 2014.
Readers are welcome to help research this issue further and document sane and effective solutions.  For example, users who solely rely on Debian and Kicksecure ™ onion services for updates may have had (partial) protection against the 2019 APT bug, but this requires investigation.
Always Up-to-date Builds
If Kicksecure ™ regularly released up-to-date builds, this would be an optimal solution for end users. However, the maintenance effort -- building, testing and uploading -- is resource-intensive and not currently feasible for the Kicksecure ™ team.
Greater community support is needed for testing proposed Kicksecure ™ package updates and major new releases, alongside an automated test suite for Kicksecure ™.
When using virtual machines, Kicksecure ™ could be configured to use the host apt-cache. Physically-isolated Kicksecure ™ could use an apt-cache running on a separate machine. apt-cacher-ng is an example implementation of such an apt-cache.
This configuration does not secure operating system updates by default over Tor, which is a big disadvantage.  It would be first necessary to determine how to configure apt-cacher-ng on the host to force downloads through Tor.
Another possibility is somehow using apt-offline to complete the initial updates of Kicksecure ™.
Building from Source Code using Current Sources
Self-created Kicksecure ™ builds from source code use current sources, thereby solving this problem. Although frozen sources have been deprecated for reasons outlined in the Build documentation, using current sources comes with its own issues.
- Such as Tor exit relays.
- Forum discussion.
- This leaks a list of installed packages to ISP-level adversaries and update servers. For example, if a user installed a webserver that is likely to be used to host a hidden web service, then this information would leak.