When developing software I find it very useful to stick to a number of rules. They are all commonly known, but it can be very convenient to have list of them. Sticking to these rules will enhance the quality of your code drastically.
It’s all about practicing questions
In part 1 of this blog data was exfiltrated from a workstation to GitHub using Git. In part 2, we’ll dive into investigating the data on a Windows 10 workstation to determine whether any sensitive data was exfiltrated to GitHub using Git. The investigation focuses on analyzing traces left on the device, excluding network activity logs.
NIS2 is on the horizon, but what should you or your organization do? Which measures need to be taken? Unfortunately the exact guidelines are not known and leave us in a state of uncertainty. The Dutch Ministry of Justice and Security is working on translating NIS2 into the Cybersecurity Act, which will replace the current Network and Information Systems Security Act (Wbni). The new law was initially scheduled end of 2024 and required all companies and organizations to take steps to comply. The start date has been postponed to early 2025.
In the era of unprecedented digitization, where technology deeply penetrates into our society and organizations, software has become the driving force behind progress. No matter which industry, almost every organization is increasingly dependent on software applications. The goal? Optimizing business processes, providing seamless user experiences, and creating new opportunities. The crucial detail of this revolution: high-quality software is essential for the success and resilience of businesses and organizations.
However, this is the part where we encounter an interesting paradox: digitization is not only an enormous opportunity, also a threat. Cyber threats are evolving at an alarming rate. Attackers constantly seek vulnerabilities to infiltrate systems and steal sensitive data. Ensuring the security of software is no longer a choice, but an absolute necessity.
When Maven needs to download artifacts from a remote repository, it logs the progress of the download. This can lead to a lot of noise in the output. Luckily, we can suppress the logging of the download progress. Since Maven 3.6.1. we can use the command-line option --no-transfer-progress to disable the logging of the download progress. There is also a short version of the option: -ntp.
In a previous blog post we learned about the default input sources that are used by Helidon SE. The list of input sources is different based on which artifacts are on the classpath of our application. When we write tests for code in our application that uses the default configuration created by Config.create() we must take into account that different input sources are used. Also here it is based on the artifacts that are on the classpath. That means that different files with configuration data are loaded, eg. a file application-test.conf when we have the artifact helidon-config-hocon and a file application-test.yml if the artifact helidon-config-yaml is on the classpath.
