The security of IT systems is becoming increasingly important as they are exposed to many potential threats through their architecture, implementation and networking. That's why we integrate Security experts into our project teams right from the start.
We see security as an integral component of our work (DevSecOps). That means establishing IT security as a quality feature from the word go and firmly integrating it into every project. For us, security is not a state of being, but rather a continuous process covering all phases of a project. That is why we integrate Security experts into our project teams right from the start. Whether it is in projects for development, data science or IT operations: security is everywhere at inovex.
Innovative IT solutions are characterized by methods and technologies that focus on flexibility, speed, openness and networking (Web, Cloud, continuous delivery, open source, open APIs, etc.). This provides the manufacturers and users of IT systems with many advantages. However, the security risk increases at the same time, because these systems move in a highly-dynamic innovative environment and can no longer be protected by regular, static checks. Sometimes, one single vulnerability is all it takes to penetrate a system and cause damage.
Although the quality assurance of IT systems can be largely automated, this has limitations when it comes to Security. The manual effort here continues to be higher because a wide range of attack vectors must be checked, for example as part of penetration tests. However, if security aspects are given enough consideration from the very beginning when defining the architecture and Software Development, the risk can be made manageable. In light of this, we have expanded our portfolio and now also offer Security competences, both to protect existing systems (audits, reviews, etc.) and for security-relevant aspects of new developments, in particular. We have a team of Security engineers on-board, who ensure that a system is or will be 'security-minded' on an infrastructure and Application level.
Threats by digital attackers
We are currently seeing three main methods of attack:
- Firstly, an attacker hacks into a digital system (e.g. through a Security gap in a Web Application or through an inadequately secured service), assigns himself far-reaching rights and encodes the data managed by the system (ransomware). Then, a kind of 'ransom' is demanded to decrypt this data again.
- The second type of attack is when the attacker obtains control over the hardware resources of a system, i.e. 'kidnaps' the computer capacity. With these acquired resources, the attacker can affect the functionality of the system, launching widespread attacks on third-party systems, e.g. denial-of-service attacks (DoS), or sending spam emails, for example. Computing capacity is deemed to be an asset in the network industry and can be used universally for – genuine or illicit – purposes.
- In the third scenario, the attacker gains access to confidential data in a system (e.g. user or customer data) to sell this on the black market or use it for subsequent attacks. The consequences of such an occurrence can have a severe impact on the reputation of a company, meaning it may be viewed as untrustworthy in the eyes of its customers and other business partners for a long time after the attack. Some companies and public institutions have specific concerns beyond these risks, for example because they possess particular data, in which criminals or politically motivated hackers may be interested. State-organized hacking with the aim of influencing political decision-making process and digital espionage that targets intellectual property such as inventions are the most prominent examples here.
Basic security awareness
When we talk about the Security of digital systems, we must first explain which general and specific security requirements need to be covered. Lots of general risks are monitored very accurately by the developers of large-scale, basic technical products and frameworks and are constantly taken into account in the update process, meaning a certain level of protection is guaranteed simply through careful IT operations. Systems that are not regularly maintained and not updated with the latest security patches are particularly susceptible to becoming gateways for attackers. This is seen time and again in global IT security catastrophes, such as the 'WannaCry' or 'Petya/NotPetya' ransomware.
Security by inovex
Digital Security could be viewed as a 'quality' issue, but it is so extensive, so dynamic in growth and so fast-paced a topic that we view it as a separate entity. Our Security team means we are able to develop and harden basic digital components, such as Web Applications and IT infrastructures in a security-related manner and thereby fulfil compliance requirements – e.g. using public key infrastructures (PKIs). However, we can also evaluate the highly innovative segments within the digital world (IoT, AI/KI) and develop strategies for their protection. The objective is always to be prepared for attacks in the best possible way and to minimize the probability of a successful attack. We can also use penetration tests to cover security gaps in systems that have been developed by third parties and help to close these.
Our Security experts know the advantages and disadvantages of pertinent Security solutions and tools and know from experience how these can be productively implemented and applied. inovex’ USP is that we are able to fill our project teams with Security experts from the very start of our development of digital solutions. These experts deal with the Security aspects of the IT systems, while also being able to undertake 'normal' development tasks. This means that Security is an integral part of the digital solution from the start of the project and guarantees the added value of the system in the long term. At inovex, we call this 'DevSecOps'.
Our services in detail
Architecture workshops with a focus on Security
Our Security engineers collaborate in architecture workshops, particularly when it comes to planning new architecture and Security issues are raised. We support our clients in developing the right architecture for an infrastructure, which is 'security-minded' and supports the automation of security-relevant processes. This is about defining the right measure for protecting the use cases, which should then be rolled out to the infrastructure. At the end, a security concept is compiled.
Support by a security engineer
Security is not a state – it’s a process. And this is why we offer the support and collaboration of a Security engineer in all security-relevant aspects from the design and development through to the final operating mode. The security engineer is your contact for all the team’s security-relevant questions and motivates the team to bear relevant issues in mind.
Architecture review with a focus on Security
If an architecture has already been developed without the involvement of a Security engineer, we review this existing architecture in terms of its security aspects. During this review, we identify and classify the architecture’s risks and propose measures to improve the Security. This review can be used to prepare for a Security audit, for example.
A reconnaissance determines all the publically accessible information about an objective or company and analyses this for possible 'information leaks'. This is because, before an attacker attacks a company, he tries to exploit any little pieces of information from public sources, e.g. addresses, emails, employees, financial circumstances, communication channels, technologies, DNS entries, business relationships, running systems or administrators. This information is often a gold mine because it can provide the attacker with information about internal procedures. We put ourselves in the role of a potential attacker and collect all the information about a company we can find on the internet.
Penetration tests are ideal for assessing the current Security status of a system or Web Application. When performing a penetration test, the publically accessible services and backend are examined specifically from the point of view of an attacker. The objective is to determine which vulnerabilities the attacker can identify and how far into the system he can actually penetrate. In addition, developers and administrators are given the assurance that security-relevant parts have been implemented correctly and the system has no known vulnerabilities. Primarily, however, these penetration tests constitute a sound basis on which our Security engineers (see also 'Support by a Security engineer') can help you to rectify vulnerabilities and improve systems to a suitably high level of security in the long term.
Automated scanning infrastructure
We establish an automated infrastructure, with which vulnerabilities are searched for and scanned automatically and at regular intervals – even during development or operation. The continual identification of vulnerabilities contributes to finding and closing vulnerabilities in good time before an attacker exploits an obvious vulnerability. For example, the OWASP top 10 risks can be automatically sought in a Web Application.
Nowadays, software has countless external dependencies on libraries, frameworks and modules. With this multitude of dependencies, it is very difficult to maintain an overview of unsecure dependencies or new vulnerabilities in these dependencies. Just one single vulnerability could lead to the entire system being at risk. A dependency check makes it possible to check whether countless dependencies of a software system have any known vulnerabilities.
To penetrate a system (web application, server, service, network, ...), attackers often exploit known Security holes or misconfigurations. A vulnerability scan should prove that the system has no known vulnerabilities that an attacker could exploit or that could generally endanger the overall Security of a system. A scan for vulnerabilities should not be equated with a comprehensive penetration test, but can provide an initial analysis of the security of a system.
It is only in the rarest of cases that a product or service is delivered or configured 'securely' ex works. This means the infrastructure, the service or the application is only as secure as its weakest link. When performing a hardening process, the configuration is examined for possible vulnerabilities or anomalies. The aim of the hardening process is to keep the attack surface as small as possible.
Emergency deployment in case of incidents
In the case of acute Security incidents, we can support companies in managing the incident and introducing practical measures (immediate, short-term, medium-term and long-term). Detailed post mortem analyses of successful intrusions are not our specialist field but we are happy to provide advice in selecting a competent service provider and initiating the measures from the results of the analysis.
Intrusion detection and intrusion prevention systems
We know from experience that attackers carry out automated scans dozens of times a day. For this reason, it is important to detect such an attack and take countermeasures as quickly as possible. IDS (intrusion detection systems) and IPS (intrusion prevention systems) are used to identify these scans. If these systems ascertain an attack pattern while observing the log files or packages, then the attacker is blocked and a message about the potential attack is sent to the person in charge.
Would you like a consultation on this subject?
Call us or send us an E-Mail. We look forward to advising you.+49 (0)721 619 021-0
Get in touch!
Head of Application Development
Our Technology Partners
inovex cooperates with a range of selected technology partners to offer our customers genuine added value: Amazon Web Services, Cloudera, Confluent, Elastic, e-shelter, MapR, Microsoft, Quobyte and SoftBank Robotics.Read more
Certified Scrum Developer Training, Scrum Basics, Scrum Training for Product Managers, Practical Agile Development, Kanban BasicsRead more