Airlines are starting to use unregulated facial recognition. This new site will help you choose the ones that don't use this technology. A digital rights group, Fight for the Future, has created a tool that helps travelers avoid flying with airlines that use unregulated FRT facial recognition at boarding. AirlinePrivacy.com helps passengers book flights where they know they won't have a facial scan taken and stored in a database. It comes amidst growing unease at airline practices in personal data use. read the whole article here: https://interestingengineering.com/a-new-website-helps-you-choose-airlines-that-dont-use-facial-recognition Google's Quantum Processor May Achieve Quantum Supremacy in MonthsMoore's Law famously held that computer processor power would double about every two years, but now, Neven's Law appears to show quantum computing's explosive, 'doubly exponential' growth.
Read the whole article here: https://interestingengineering.com/googles-quantum-processor-may-achieve-quantum-supremacy-in-months https://cisofy.com/lynis/
Lynis is a battle-tested security tool for systems running Linux, macOS, or Unix-based operating system. It performs an extensive health scan of your systems to support system hardening and compliance testing. The project is open source software with the GPL license and available since 2007. Example screenshot of a Linux security scan with Lynis Security scan with Lynis (click for full image) Project goals Since Lynis is flexible, it is used for several different purposes. Typical use cases for Lynis include: Security auditing Compliance testing (e.g. PCI, HIPAA, SOx) Penetration testing Vulnerability detection System hardening Audience and use cases Developers: Test that Docker image, or improve the hardening of your deployed web application. System administrators: Run daily health scans to discover new weaknesses. IT auditors: Show colleagues or clients what can be done to improve security. Penetration testers: Discover security weaknesses on systems of your clients, that may eventually result in system compromise. Supported operating systems Lynis runs on almost all UNIX-based systems and versions, including: AIX FreeBSD HP-UX Linux macOS NetBSD NixOS OpenBSD Solaris and others It even runs on systems like the Raspberry Pi, IoT devices, and QNAP storage devices. How it works Lynis scanning is modular and opportunistic. This means it will only use and test the components that it can find, such as the available system tools and its libraries. The benefit is that no installation of other tools is needed, so you can keep your systems clean. By using this scanning method, the tool can run with almost no dependencies. Also, the more components it discovers, the more extensive the audit will be. In other words: Lynis will always perform scans that are tailored to your system. No audit will be the same! Example: When Lynis detects that you are running Apache, it will perform an initial round of Apache related tests. Then when it performs the specific Apache tests, it may also discover a SSL/TLS configuration. It then performs additional auditing steps based on that. A good example is collecting any discovered certificates, so that they can be scanned later as well. Audit steps This is what happens during a typical scan with Lynis: Initialization Perform basic checks, such as file ownership Determine operating system and tools Search for available software components Check latest Lynis version Run enabled plugins Run security tests per category Perform execution of your custom tests (optional) Report status of security scan Besides the report and information displayed on screen, all technical details about the scan are stored in a log file (lynis.log). Findings like warnings and suggestions are stored in a separate report file (lynis-report.dat). Lynis tests (controls) Lynis performs hundreds of individual tests. Each test will help to determine the security state of the system. Most tests are written in shell script and have a unique identifier (e.g. KRNL-6000). Interested in learning more about the tests? Have a look at the Lynis controls and individual tests. Flexibility With the unique identifiers it is possible to tune a security scan. For example, if a test is too strict for your scanning appetite, simply disable it. This way you get an optimal system audit for your environment. Lynis is modular and allows to run your self-created tests. You can even create them in other scripting or programming languages. Lynis Plugins Plugins are modular extensions to Lynis. With the help of the plugins, Lynis will perform additional tests and collect more system information. Each plugin has the objective to collect specific data. This data is stored in the Lynis report file (lynis-report.dat). Depending on your usage of Lynis, the collected data might provide valuable insights between systems or between individual scans. The plugins provide the most value in environments with more than 10 systems. Some plugins are available in the downloads section. Extra plugins As part of our Lynis Enterprise offering, the core developers maintain a set of plugins for our customers. The data that is collected centrally (SaaS or self-hosted), provide additional insights, such as available users, processes, and network details. Another important area is compliance testing, where the data points help to test against common standards and hardening guides. Lynis plugins overview Supported standards Other tools typically use the same data files to perform tests. Lynis is not limited to a specific Linux distribution, therefore it uses the knowledge of 10+ years from a wide range of sources. It may help you to automate or test against security best practices from sources like: CIS benchmarks NIST NSA OpenSCAP data Vendor guides and recommendations (e.g. Debian Gentoo, Red Hat) |
Author: <see article>
These links serve as tributes to those who have written them. Please find contributor details in the links provided Archives
April 2024
Categories |