Security
of the contamination was , where else that contaminated ingredient might be used , and so on . Even if the contamination is minor , it still needs to be addressed , and what the resolution process is going to be specific to the type of contamination , where it originated from and how the contaminated ingredient is used .
Bolstering security
But then , the question emerges : how are the consumers protected from purchasing and eating this botched batch of cakes ? And who is responsible if such spoiled ingredients are incorporated into the cake ’ s batter ? This ambiguity can quickly take the situation from bad to worse , and therefore , requires organizations to be intentional about the ingredients they use ; knowing what is being used and where they come from .
To circle this back to software security , manufacturers also need to be attentive to the software components they use within their applications . The reasons for doing so are multi-fold . On one hand , it is fundamental to building and protecting trust associated with your brand . If your cheesecake is found to be the source of widespread food poisoning , or your broken software leads to a massive breach of sensitive data , it goes without saying that you will lose existing and potential customers . Equally , it is crucial in ensuring you are protected legally . Failing to dedicate the necessary time and resources into bolstering an application ’ s security can lead to significant financial losses in the form of lawsuits or regulatory fines . In truth though , a moral responsibility to protect end-users from using software components that may contain software security vulnerabilities or software license concerns should be factored in too .
scw-mag . com 15