security-with-what-time-my-continuous-integration-backlog-is-overflowing

 

hacking continuous integration

 

There are numerous security measures a developer can perform but nearly half (48%) of all developers say they don’t have enough time to do so. They know security is important but with an often demanding schedule they end up concentrating on developing for functionality instead of security. This kind of thought process can lead to vulnerabilities in code and containers alike. “Security? With what time? My continuous integration backlog is overflowing.” We hear you. Security and integrity is a time-consuming responsibility but CodeNotary makes it easy for you to implement.

 

Project Juggling and Development

 

With time in limited supply, spending it wisely is a high priority for developers. That and effective time management is a widely sought after skill as well as an industry best practice. Coders are incessantly driving to maximize their productivity.

 

Never ask a developer, “Really, how many lines of code did you produce today?”

 

Speed in DevOps clearly has its advantages but it can also lead to compromises due to hastily published misconfigurations and errors being put into production.

 

Coding is a complex skill. It takes time to do it right. Considering miscommunications and everything else that can cause project backlogs to pile up (here’s a funny cartoon about it), time is in an ever-increasing shorter supply. This often leaves security concerns to become afterthoughts, if even that.

 

Fallout from Continuous Integration

 

With the never-ending battle between white hats and black hats and the constant march towards continuous integration inevitably leaving new zero-day exploits in its wake, new security measures are constantly emerging.

 

The good news is you can employ some good practices to help significantly mitigate your security risk.

 

The bad news is that they all take more of your time and tip the balance away from you doing what dev does best – writing code. For example, this list by DevSecCon is a good set of 9 recommendations on how to secure containers before deployment. But what the list doesn’t do is help you to get more security in less time, which is the ideal.

 

A Solution for Time-Crunched Devs

 

Here’s one solution we came up with to help you maintain 100% confidence in your containers and gain security over your build environments. CodeNotary’s 1-step verification open source software takes seconds and delivers blockchain backed reputational liability protection. Additionally, it’s used in your continuous integration pipelines allows you to increase your productivity by spending substantially less time doing security reviews and remediations after breaches. You know instantly if your code has been compromised. Today with the immutability of blockchain, code integrity guaranteed by CodeNotary is a lightning fast, pervasive and repository agnostic reality.

 

Check out our Jenkins Integration here or test drive CodeNotary for yourself with a complimentary 15-day trial. And bonus, if you’re an OSS and non-commercial developer, your license is free….forever.

 

Show Me How It Works

 

References

https://techbeacon.com/security/get-real-container-security-4-rules-devops-teams-should-follow

http://www.devseccon.com/blog/2018/11/05/9-practical-steps-to-secure-your-container-deployment/

https://techbeacon.com/security/32-application-security-stats-matter

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.