ISO 27001 is an international standard with global recognition that gives organisations a clear framework to follow for their Information Security Management System (ISMS), it is also a business enabler.
Infomentum is very proud to achieve the internationally recognised certification of ISO 27001 in February for the second consecutive year. The certification has confirmed our compliance to the standard with no non-conformities identified.
Our lives might be going digital, but what does that mean for the physical environments in which we live, work and play? Whether checking air quality or preventing street violence, what is the public sector doing to harness new technologies that deliver a better citizen experience; not just in interactions with services, but in the infrastructure that supports our lives? From housing to transport, how are these connected communities being brought to life by Edge computing and IoT in the UK?
In the second of our series on the public sector, digital transformation and Smart Lives, we are looking at cloud computing. At a time when government organisations struggle for funding, digitalisation offers a way of delivering services to users in a more cost-effective manner. Cloud is the foundation of that transformation. As a concept it has been talked about for over a decade yet adopting it can be a challenge for cash-strapped public services. What stops the sector from accelerating cloud use to unlock its benefits?
Public services, like many sectors, are wrestling with how it can make the most of the opportunities on offer through digital transformation. Over the course of the coming weeks, we’ll look at some of the most common challenges faced by the public sector. Our blogs will cover why government has been slow to adopt digital transformation and move to the Cloud, how Edge computing and the Internet of Things can be integrated into everyday life, and what 'Smart Lives' really means. Today, we are considering identity verification, and whether it is the future of the public sector’s digital transformation.
Who are you? Can you prove it?
December. The time of year when people stop consuming the budget and start consuming traditional Christmas cakes. However, December is also the time of year to look back and reflect on the previous 11 months.
In Part 1, we talked about picking the tools for our first foray into the world of headless Content Management System (CMS) architectures, during our project with Fudgelearn. We had other options on our radar, but we decided that WordPress was the CMS that fit in best with our requirements. These were the main ones:
Web development is accelerating at an incredible rate - new frameworks seem to pop up every day. Whilst this is exciting (at least to a front-end geek like me!), it can be difficult knowing which new tools are any good and which ones you should be using.
In my last article, The evolution of test documentation; lessons learned from implementing Cucumber, I explained two things. Firstly, how we at Infomentum have adopted Behaviour-Driven Development to define test scenarios, and secondly, how we use Cucumber JVM as an implementation platform for running these scenarios as automated tests.
Generation C is not a group defined by their age; they are defined by their attitudes, behaviour, shared interests and constantly connected digital lifestyle.
A wise man once said "If you are going to dive head-first into DevOps, better pack a parachute". Aside from the fact that this man was me, the point is still valid.
Infomentum had started maturing into a DevOps culture, which involved the developers using tools normally associated with DevOps to solve development problems. We were calling it DevOps for several years, even though the actual DevOps culture, practices and support were not in place. The changes made were effective at enhancing the development lifecycle, but were completely separate and sliced off from the rest of the organisation. This meant that infrastructure needed to catch up so that the DevOps practices could be fully utilised throughout the company. The major issue with DevOps is that it really is all or nothing; as soon as you have segregated processes and half-utilised technologies, the power of DevOps is completely negated.
