Industry: Supply Chain & LogisticsTechnologies: Java, Azure DevOps, Terraform, Helm, Azure Kubernetes Service (AKS), CrossplaneServices: DevOps Enablement, CI/CD Pipeline Design, Azure Infrastructure Architecture, Agile Transformation Overview A leading organization in the supply chain and logistics industry engaged Keyhole Software to lead a major transformation of its internal IT operations and software delivery practices. The organization was operating without a DevOps …
What if your Azure cloud computing setup could do more for less? Many businesses unknowingly overspend on cloud services due to inefficient configurations and underutilized resources, losing both money and performance potential. The good news is that with the right strategies, you can optimize your Azure cloud computing environment to be smarter, faster, and more cost-effective. This post highlights seven …
Platform engineering services from Keyhole Software include internal developer platforms, cloud-native infrastructure, DevOps pipelines, security, and observability. Empower your teams with scalable, automated platforms.
This is Part 3 of our series on creating an FHIR API using Google Cloud’s offering. In the last installment, we began implementing an FHIR using GCP. We covered creating both the BigQuery resources and your FHIR repository resources. if you missed Part 1 and Part 2, be sure you go back to read those – they’re critical to understanding!
This time, we’re continuing the implementation. I’ll explain the authentication methods, and we’ll also tackle populating data in our FHIR repository.
Developing custom applications is one of the hardest professional endeavors, and making them secure is even harder. Malicious actors are constantly changing tactics and strategies, which, unfortunately, makes it impossible to completely eliminate any security threat.
There needs to be a balance between delivering features quickly to meet business objectives and mitigating security risks. Thankfully, these two goals are not mutually exclusive. This blog post dives into the top mistakes that can be made while developing custom applications.
These recommendations are different from what would commonly be seen in an OWASP list, and they should be used in addition to whatever security practices and procedures are already in place by an organization’s infosec department. These recommendations are also written from an application architect’s (rather than an enterprise infrastructure) perspective, so most of them aren’t covered by existing security checklists.