that <\/em>would be a game changer!<\/p>\nThose with a keen interest in these things will have noticed a radically different approach to authentication in the 5G standards. This change is to better support new concepts, new business models, IoT (which is both of the above) and NFV, as well as the vastly increased demand for network authentication that new 5G related services will bring about.<\/p>\n
Let\u2019s stop and think about NFV for a moment. Using standardised hardware platforms and deploying only the functions needed is a very attractive prospect for MNOs. It promises to change the cost of doing business quite dramatically. MNOs in smaller markets may even think about using managed services in the Cloud for hosting and operating the core. This is another game changer for the way they can do business in the future and give their customers access to 5G services much faster than was hitherto possible.<\/p>\n
Now I move on to my worry point and I am glad to also say that there is a solution to my worries, but I am not yet seeing a groundswell towards adoption of the solution I have in mind. This is my concern. MNOs have traditionally taken great care to safeguard their keys, algorithms and sensitive business logic. The vital network credentials used during both SIM provisioning and then for network authentication have always been subject to strict security policies and processes. This is for a very good reason because the possibility of having network keys or algorithms compromised is probably the highest risk to business continuity that an MNO faces. So why would anyone risk having their crown jewels in a virtualised function which may even be part of a hosted Cloud solution? I know I wouldn\u2019t. This seems like a deadly scenario which ends where I started and the CTIO asking \u2018where exactly did I leave my keys?\u2019 Too late to ask that question now!<\/p>\n
There are solutions available and the one I favour most is creating a safe for the crown jewels. Yes, I know falling back on a hardware solution bucks the trend of NFV but there are some things I still really want to see kept safe and sound in a protected, tamper proof piece of hardware. The solution \u2013 at least in part \u2013 is available today and used in many adjacent industries. Using a Hardware Secure Module (HSM) to store Mobile algorithms such as Milenage, COMP-128 and remote SIM OTA custom key derivation algorithms safeguards crucial data. By also deploying Business logic such as HSS eKi decryption for use with Milenage, contained within the HSM, the Ki is never used in an unencrypted form externally. The HSM can also support the generation of SIM provisioning credentials and transport encryption, from Ki to PIN\/PUKs generation, all in one request. Include SIM OTA secured payload assembly for both UICCs and eUICCs for example.<\/p>\n
Having adopted this principle, MNOs can even consider the outsourcing support of internal systems used for SIM production containing sensitive material. Very many MNOs have already outsourced their SIM provisioning and in this situation, the use of the HSM provides them with a way of reclaiming control of their keys but still have the production facility outsourced. To put this another way, would you hand your keys to someone else to unlock your house or car on your behalf? Of course not, so having an HSM allows you to do it yourself without sharing your secrets!<\/p>\n
Together, these are the security methods which are needed in the 5G NFV environment and maybe its just a matter of time before MNOs arrive at this same viewpoint, but for the current rate of adoption is still worryingly low. The need to secure business continuity is the main driver for the adoption of HSMs into the SIM provisioning and authentication processes but once done it also opens new business and revenue opportunities for MNOs. We all see that a lot of the news items about 5G focus on the emergence of new business models whereby MNOs forge new partnerships with players in other industry verticals to really make IoT happen.<\/p>\n
Monetising the SIM as an asset is really important for MNOs in the 5G world and offering a heightened level of security over other wireless access technologies will be a major factor for those organisations developing industrialised IoT applications. Many of these new business partnerships will be deeper and more rewarding, as partners \u2013 call them external service providers \u2013 can have access to sensitive material but are in a position of elevated trust to do their own provisioning. In the world of remote SIM provisioning (RSP), I think this opens up limitless new possibilities for service delivery which allow MNOs to be serious players in the IoT market. Think of it this way: allowing new partners access to key material outsources trust without the MNO losing control. Smaller, specialist RSP partners, inherit this level of trust and the MNO will know that the integrity of the sensitive data is guaranteed by use of the HSM. Some MNOs are worried about the impact RSP may have on their business. More forward-thinking MNOs will see RSP as a major opportunity to expand their business relationships, just so long as they keep the commercially sensitive credentials safe and sound.<\/p>\n
Making this happen isn\u2019t simply just a case of buying a standards compliant HSM. It is firstly understanding how to apply the necessary business logic to the HSM and then to integrate this into current support systems that is more of the challenge. The rewards of doing this though are sufficiently high for it to be worth the challenge. At Azenby we would like to help MNOs and MVNOs of all sizes make the transition towards this new level of security for network credentials and to then exploit the new business opportunities this can open up.<\/p>\n
If you would like to learn more about how we can help with this journey, why not get in touch<\/a> with us today. The sooner the journey starts the less chance of those keys being lost!<\/p>\n","protected":false},"excerpt":{"rendered":"I have a nasty feeling that more than one red faced CTIO will be asking this question in the not too distant future. It won\u2019t be the house keys or the car keys that will be missing down the back of the sofa. This time it will be far more serious. Here is the scenario […]<\/p>\n","protected":false},"author":5,"featured_media":2563,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-2562","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pointofview"],"_links":{"self":[{"href":"https:\/\/azenby.com\/index.php?rest_route=\/wp\/v2\/posts\/2562","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/azenby.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/azenby.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/azenby.com\/index.php?rest_route=\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/azenby.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2562"}],"version-history":[{"count":0,"href":"https:\/\/azenby.com\/index.php?rest_route=\/wp\/v2\/posts\/2562\/revisions"}],"wp:attachment":[{"href":"https:\/\/azenby.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/azenby.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2562"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/azenby.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}