Monday, October 12, 2015

Introducing the Apple iRing

Apple recently applied for a patent in the United States for what could be called an iRing. This initially sounds like a goofy idea but hold that thought!

Image credit: US Patent and Trademark Office
Image credit: US Patent and Trademark Office
Apple has designed a ring will incorporate a motion-sensing accelerometer and gyroscope. This essentially means it will understand 360-degree movement, allowing hands free gesture control. A great feature for gamers it would seem.

The iRing is worn on the index finger with a provision for control by your thumb.
Apple has also separately announced what it calls the iPad Pro, a 12.9 inch tablet with an A4 screen making it perfect for reading documents without need to navigate back and forth on the page. The iPad Pro has been built with the idea that you would perhaps use a companion keyboard or the first ever Apple Stylus. It is therefore a natural progression that you could use the iRing as a companion device.

A use case that I can clearly see is where an iRing can be used to help scrolling between pages, or perhaps even used to ‘cut and paste’ an article online.

These gestures could also be a great breakthrough for disabled users, making it easier to use such tablet devices without having to grip the actual hardware. Much like the Apple Watch, which allows you to receive alerts and messages, features that I believe aren’t that attractive.

But having an Apple iRing on my index finger does allow me to use the microphone and have ‘hands free’ conferences while driving for instance.

Perhaps controlling my Apple TV to select and change channels is also going to be really handy (pardon the pun) feature.
But the most attractive use case will be in payments and the iRing’s use with Apple Pay, the mobile payments and digital wallet service.

For a glimpse at the future, take a look at London-based startup, Kerv.


This startup has created a ring that uses near field communication (NFC) technology that is often built into smartphone.

When a user travels on the London tube or buys a morning coffee, they simply wave the Kerv ring at an existing contactless terminal.

The iRing – if it is released – will be used for many things, but for me the key reason I would wear this is that I don’t have to get out my phone or wallet to make a payment.

Theoretically, with the use of a biometric thumb print, then you can also control the valid usage of this wearable device.

I’m sure there are digital teams at the 'big four banks' that are potentially adding this to their future mobile roadmap. While I’ve never been keen on an Apple iWatch, an Apple iRing makes sense and I want one.

Thursday, October 1, 2015

​Fintech Interview: Andrew Colliver, CEO, Banjo


David Gee chats to Banjo CEO Andrew Colliver about how the online lender intends to take on Australia's big four banks.

Banjo CEO Andrew Colliver
Banjo CEO Andrew Colliver
Banjo is a new Australian startup created by three former National Australia Bank executives, Andrew Colliver, Julian Hedt and Stephen Murphy.

David Gee sat down with CEO Andrew Colliver to discuss how the online lender of secured and unsecured loans to small businesses – which raised $7.5 million last month – intends to take on Australia’s big four banks.

CIO: Where did you get the inspiration to start Banjo and how are you different from the banks?

Colliver: We leverage the power of data to obtain a more holistic view of a businesses’ position so we can approve more loans.

Our logo is a folded $10 note, and Banjo Paterson inspired the name. The concept for establishing a marketplace lender such as Banjo [popped into my head] during a ‘make over’ of my front and back yard.

Over a coffee with my two co founders [Stephen Murphy and Julian Hedt], I remember both of them saying that I needed to understand that: firstly, we were building a technology company with a financial services offering; and secondly, a symbiotic relationship between the business and technology was fundamental for success.

All of our people irrespective of job role are co-located to solve common problems. From inception, we have built an organisation totally focused on seven principles.
  • Leveraging data to remove friction between the customer and the institution
  • Prototyping and constantly evolving every aspect of the customer interaction. Not just optimising the experience but looking to revolutionise it
  • Mobile as a core competency
  • Originating clients without concerns of the costs of a large branch network
  • Being channel agnostic. Simply, use the channel the customer uses
  • Establishing a symbiotic relationship between software developers, executives, business development people and marketing
  • Risk management and compliance monitoring solutions implemented at level equal to or greater than any mainstream bank, and available in real time with minimal or no human intervention.

CIO: Based on your own research, what is the customer experience like for businesses and what benchmarks are you trying to beat?

Colliver: Post-GFC, there has been a global trend of a growing disparity between banks and small businesses whereby demand for small business loans has exceeded supply. More onerous restrictions have been imposed on borrowing arrangements; the application takes too long and processes are too difficult.

It is also evident there has been a growing spread differential between home loans and small business loans, with small business loans being charged 200 basis points over the average cost of a home loan.
 
A survey from an established market place lender in the US revealed that for every 10 customers, 6 considered borrowing from banks and 4 of those 6 did not end up applying due to the perception the process is too difficult and will take too long.

In Australia, a business credit card can take 7 – 10 days, and a typical business loan will could take 30 – 60 days.

Marketplace lending can provide a better solution to the borrower. If you review the daily life cycle of a small business client, they have a series of tasks that need to be done efficiently. And 40 per cent of SMEs apply for banking services after 6pm.

However in Australia, our experience shows peak usage at 10am and 4pm with applications also flowing in at these times. We also receive a number of applications and queries on weekends, presumably when small business clients catch up on their paperwork and process matters for their business.)

So when you have ‘financial technology’ platforms such as Banjo being totally designed to take banking services to customers when and where they need it, regardless of device (mobile, tablet or PC) and remove the frustrations of paperwork…this becomes a powerful value proposition.
Customers’ expectations for anything, anytime, anywhere banking was our foremost design parameters from inception.


CIO: What process did you follow to build the offering?

Colliver: To become an online marketplace lender, we focused on 4 major pillars all executed in parallel:

1. Building a modular technology platform incorporating the best of breed off the shelf systems melded with our own proprietary systems using technology to enable scale and operating leverage.

2. Unlocking value and creating liquidity for buyers and sellers through the establishment of the Banjo Small Business Fund, offering a targeted fixed income coupon of 8 to 10 per cent per annum for corporate and wholesale investors.
3. Build a value proposition across product type and user experience that is consistent with helping the customer complete their daily tasks efficiently…where and when they want to.

4. Built our company from inception around the brand. For instance, the brand was not retrofitted to the company once it was built. We commenced with a brand platform, followed by a brand narrative and brand identification process, followed by the creation of brand assets and so on. It was a total build.

Of these steps, 1 and 2 were the most difficult, closely followed by raising seed funding for the business.


CIO: You have engineered your solution to maximise provide both simplicity and speed. Was it harder to break established norms and achieve simplicity?

Colliver: Post-GFC, large banks globally focused on the strategic imperatives of risk management, and adapting to a new regulatory compliance and capital regime. Cost reduction initiatives tackled flat line revenues in a low consumer and business growth environment.

In every other financial shock, the banks could rely on long tested means and methods to respond to a conventional value chain. And they did again.

Yet at the same time, the building blocks of the internet of things (IoT) were gaining traction improving information connectedness, scalability, speed and driving the costs of technology stacks down to levels unheard of ten years ago.

It was only natural that new entrants leveraging technology to focus on taking banking services to clients in a relevant and convenient manner would fill the gap.

Even today, most of the technology investment by banks is going into compliance and retooling of core legacy systems rather than the user experience and servicing the needs of the client.

For Banjo, we did not need to deal with retooling core legacy systems or transitioning existing systems to a new modular technology platform. We could review what the customer was seeking, and build a customised solution.


CIO: Without giving away too many secrets, could you talk about your cost to income ratio and roughly how this compares to the big banks?

Colliver: Our cost structure would be approximately 350 basis points lower than a mainstream bank. The cost savings are predominantly in the absence of a large branch network, and lower people costs across administration, collection and processing role types.


CIO: Given that you are a startup and trying to build a brand. How do you plan to compete with the bigger players? Is there a social media strategy that you are adopting or is this relying more on expert referrals.

Colliver: We have a very detailed digital marketing campaign, and a ‘business to business’ channel management strategy involving strategic partnerships with accountants, and other 3rd parties interested in assisting SMEs achieve their goals. We are currently in discussions with a number of 3rd parties.

There are 2 million SMEs in Australia and 51 per cent do not have a business lending product at all. The SME market is estimated at $250 billion in Australia, with compound annual growth rates of 4 to 5 per cent.

But there are a large number of SMEs in Australia that either do not have a home to offer as collateral for a small business loan or they would prefer to not provide their home as collateral.
In some ways, we are trying to expand the $250 billion small business lending market by offering access to finance to those SMEs that are using credit cards or cash reserves or family loans, and our marketing may not compete head to head with the bigger players.


CIO: Have you made much investment into analytics to understand your loan portfolio and gain greater insights into credit risk management?

Colliver: We have incurred significant investment in analytics to understand our customer interactions through our customer contact management system; to understand our clients through website usage; and to understand our clients holistically in the operation of their businesses.

As mentioned above, we have Banjo Score, which is a good example of our investment in this space. We have a sophisticated call centre, Salesforce contact management system, combined with data gathered from Google Analytics and our own database.



CIO: What’s the idea behind the selfie? Other starups such as We Chat using such approaches to validate a transaction.

Colliver: We wish to remove friction between Banjo and the client. That means the elimination of paper, and we wished to avoid a person seeking validation of their identity in a branch or Australia Post office. Our aim was real time verification online. We have witnessed Airbnb and others successfully use this approach over many years.


CIO: But as you already have a photo of the driver’s license, what purpose does this serve?

Colliver: Security is paramount, and we wish to mitigate against identity theft. The person applying needs to be the owner of the licence. In a 3 director company, the other 2 directors need to consent to the borrowing and we need evidence of their identity and consent. (This is the same for where this is a partnership entity or a complicated trust vehicle.)

http://www.cio.com.au/article/585888/interview-andrew-colliver-ceo-banjo/?fp=16&fpid=1

A guide to the little jobs that will make big data work


A guide to the little jobs that will make big data work

[Blog post] Time to get your hands dirty.

Big data is one of the more glamorous terms in today’s IT vernacular, but in reality making it work is about small dirty jobs that take up a lot of resources for little immediate return.
As business adopts obsessive focus on ‘the customer’, there is a clear divide opening up between companies such as Amazon and Uber that run their businesses on analytics, and the silent majority simply trying to do things a little bit better.
The secret to staying on the right side of this gap is investing early into the little things, like metadata governance, standardisation and data glossaries.

Here are a few simple tips to guide the formative days of your business’s big data future.


Cleaning up the metadata

The big data holy grail for enterprises is a single customer view.
But the reality is that most organisations probably have around eight to 10 different customer databases that all exist to support different transactional systems. Each customer probably has a different ID in each of these accounts.

This is only going to become more daunting as the internet of things becomes a day-to-day reality and sensors are used to detect a customer instore, track their browsing behaviour and make them offers via their devices.

We have to remember that big data usually hasn’t been cleaned up and integrated into a single source of truth – indeed the opposite is the case.

To understand what is in the data lake, we need high quality metadata to track the various data stores and to distil some meaning from them.


Metadata Tsars

This is where good quality governance becomes critical.
Most enterprises have some form of data governance, but its focus is usually restricted to higher level priorities than metadata.

But you really can’t make any sense of the vast amounts of data unless you have a comprehensive metadata management approach.

This means taking on historical and headache-inducing problems like data types and data names that are not always consistent, like dates being stored as variable character fields.

Correcting these is a significant exercise with often little to show for it until a sizable investment has been already made. Unfortunately these are jobs that can’t be avoided.


Data lakes not data dumps

There is no point in building a data lake if this information can’t be accessed. That is a data dump.
Enterprises have traditionally struggled to implement data warehouses.

At best they have been a reasonable place for basic reporting systems. At worst, the shortfalls have resulted in a proliferation of these environments and the truth is that most enterprises now have a number of data warehouses.

The current architecture landscape would appear to be splintered into a number of separate data stacks.

We have learnt this lesson so let’s not repeat the same mistakes when it comes to big data.


Think like a librarian

The right approach is to do what librarians do and ensure you establish a data glossary to catalogue the enterprise data sources.

This does not need to be all-encompassing and you do not need to boil the ocean. Instead you can build a common data set of critical business data elements. What you will be focused on will be enriching the catalogue so sources are noted and applications that use this data are tracked.

Like a library, this enables sharing. Thus anyone in the business can now use their own BI tool of choice to access a shared and validated database.

For financial services, it is also critical to maintain data lineage, and in essence that means that regulated data is never deleted. Therefore if we find an issue and want to correct this, we need to maintain a history of these changes by appending rather than overwriting.


Elephants are afraid of mice

Doug Cutting’s daughter had a toy elephant that was named Hadoop - and that inspired the name of his influential big data product. But most of us would think of elephants as giant marauding beasts in Saharan Africa.

I’ve often heard that elephants are afraid of mice and in the data world at least this seems to hold true.
A giant Hadoop database cluster looks all powerful and strong, but without the small things like high quality metadata being implemented, the elephant is much weaker than one would expect.

When it comes to big data the small things really matter.

What every Board Member needs to know about Advanced Persistent Threats?


You have been asked to present next month to the board about the enterprise readiness for Advanced Persistent Threats. From what you understand it appears that, either the Chief Risk Officer, External Auditor or a ex colleague of the Board has made this suggestion.

Unfortunately you really don’t know what level of awareness the board members have about Advanced Persistent Threats. With trepidation you start to prepare for this, and the first question is how honest should you be?

Then you wonder about opening pandora’s box and making this a moment that you will regret.



Honesty is the only policy

 While you don’t want to incite any panic, it is all about getting the balance right around being confident in the approach that is being adopted, but also realistic to not provide any suggestion that your approach is bulletproof.

Yes, be honest. The worst situation would be to leave the board with the perception that everything is under total control. In the same vein you also never want them to think it is out of control.
For most of us, we aren’t good at lying and this will show in our expression. I’d hate to be in that situation. Honestly is the only policy.

Start at the Beginning
It is critical that the board gets it that an Advanced Persistent Threat is not a virus that can be simply addressed. Instead it can take many forms and the best ones morph to use different attack vectors.

This could be started with a simple virus infection, or malware that comes from an email or even code coming from a USB thumb drive. The board themselves are perhaps also part of the targeted group that hackers look to exploit.
That email from a board member’s personal pc at home to the CFO, could indeed be the mechanism to penetrate to the senior executive. Once this is understood that the scope is as wide, any reference to the need for education is a really great angle to ensure is shared.



The APT Lifecycle

What is going to help is use as much as possible ‘plain english’ and explain that these APT threats while using various approaches to get into an organisation, have an objective to remain undetected as long as possible.

Thus admitting to the fact that it is possible that these may indeed be already in the enterprise, collecting sensitive information and assessing when to take action. In your defence you can explain the measures that are in place to address this:
  • We have a ‘state of the art’ firewall to restrict access to your corporate network.
  • Endpoint software is deployed on all devices to prevent and detect malware
  • Strong passwords with two factor authentication is in place
  • The enterprise has strong Privacy and or PCI measures in place to protect sensitive information
  • Acceptable Use Policy is in place for all staff and they understand that Cyber Security starts with them no clicking on the wrong links
Wearing the Black Hat


Moreover it will be critical to demonstrate that we have internal staff and partners that we ask to wear the black hat. That means we are doing our own monitoring for vulnerabilities – reconnaissance if you like.

The resource will use all the dirty tactics of phishing, social media engineering attacks and perhaps even dumpster diving. We could also use a tactic to try mock attacks. This could involve a mock spear phishing attack and seeing what happens when random staff are sent a false message with an attachment etc.

Understanding the network and the perimeter and which ports are vulnerable. To this end I’ve met with Security companies that are pitching to work with me that have conducted such an exercise and they can highlight potential risk areas, even without breaking the law.

A random audit of SIEM logs can also provide some interesting insight. If your team is not closely monitoring these, then it is likely that any clues are being missed. Taking that sample and checking that any items that should be deemed suspicious was noted would be a great exercise. This is all about ‘trust but verify’.

  Be confident but not smug

The board will appreciate your humility and that you are taking all measures to stay on top of any threat from Advanced Persistent Threats.
Being confident about the approach and having the board now fully informed, they are now in a position to re-evaluate the Enterprise Risk Appetite.
(Phew) you can keep your job – for now at least.

Wednesday, September 30, 2015

Security Degustation or a simple Sandwich






In most organisations we are using a combination of waterfall or agile development to deliver new business functionality. Unfortunately it is also true that security is not the first consideration, in fact it is often an after thought.


For most large-scale projects, there is a consistent use of SDLC or waterfall approach. These instances have a traditional requirements stage and then formal testing to validate that the specs are met. Such large-scale projects always have a Non-Functional Requirements document that includes “Security” as one key element.

We can think of Security being more akin to a ‘degustation’ course set and there is an expected additional course (stage) that is dedicated for the security test to ensure all needs are met. For such critical projects, there may be time pressure but adequate security testing is usually performed.

Agile Security

In the agile world, a series of sprints are undertaken to build functionality and by definition the requirements are not all known in advance. The requirements are embodied within stories that are built and developed in each sprint.

As the design is made on the run, it limits the bandwidth and opportunity to consider security needs of any new system. Indeed there is a strong temptation to believe that it can be bypassed.

Time is of the essence for nearly every digital project that I have seen. Thus the team naturally wants to deliver these new features into production as quickly as possible.

Let’s remember that a philosophy of MVP or minimum viable product is preached, therefore the team is pushing to not over engineer and keep development to the thinnest possible slice.



A Security Sandwich

The so-called “Security Sandwich” approach is all about trying to adhere to robust security within the agile framework. For example this would mean that you add stories that include the “security” risks and have these integrated into the development process.

To write a security user story, is however not that easy for the average agile developer. Such efforts require a very strong holistic sense of how this story fits into the overall picture. Thus understanding the overall threat model is part of the developer’s responsibility – this means that we have to look at what threats exist and what their impact might be.

A risk-based approach will always assist in getting to the real essence of what the security story needs to cover. This is especially the case as it would often be politically incorrect to have the release delayed due to a ‘security test’.

In the agile world, there is an expectation of continuous releases and delivery.
Compounding this is the fact that security tests usually are about vulnerabilities that exist between different systems and components. As such test automation is going to be tricky.


Best Practices for Agile Security



This is a developing area and there are no simple security metrics that can be pointed to as the ‘answer’. Best practice is about ensuring that security stories are part of the sprints and not a discrete activity prior to the release going live. You just have to design it right.

Instead it is only possible to tackle an agile approach to security – where this is about testing as we go and it is not a ‘big bang’. The developer has to take this task on and not rely on a specialized security team to give the ‘all clear’ at the end. Thus developers are both debugging and also finding security vulnerabilities.

Ideally this occurs on a daily basis as the builds are being developed.

The dual objective is that we want to build software both quickly and also securely. It is indeed a Security Sandwich.

http://www.cso.com.au/article/584836/security-degustation-simple-sandwich/

Sunday, September 27, 2015

How do you know when an employee is going to leave with all your corporate data?


As the boundaries between work and leisure blur, it becomes an increasingly problematic question to answer. No longer it is the case the all files remain physically within the building; in truth corporate data is accessed from many locations and devices.


The real question remains – do we know when an employee is going to leave with corporate data? What clues exist to help you prevent this from happening?
I do recall some analytics that were run around which employees were the biggest users of external internet access. At the time it was just my team monitoring whether the recently changed policy of removing usage quotas was being abused or not.

My own observation at the time that there was a correlation between most of the Top 10 users and what I knew from Management Committee meetings to be many of the lowest performers in the organisation.

It’s the Quiet Ones

Often proven to be true, it is the individuals that you don’t suspect that actually are the staff that you need to actually monitor more closely.

This is particularly true when it comes to employees that are about to leave. Often they are the ones that are not taking leave. They may also be the diligent ones that are always working back when others have already left the office. Or in the case of mobile workers they are the staff that are logged in from home.

I’ve also seen firsthand that what the normal person who consider to be acceptable use of corporate assets – actually gets misinterpreted and remember a staff member who ‘borrowed” laptops to fund his gambling habit. Yes, and I did say ‘borrow’, that was the way he explained the situation.


However at the time I was more concerned about the potential data loss than the physical asset.


Silver Bullets

For most organisations, the approach to stop employees leaving with your data usually revolves around deployment of a Data Loss Prevention (DLP) Tool and or Email Filtering Tools. The real question is how effective are such tools in preventing the company’s secrets from leaving the building?

There is in reality very few silver bullets, these tools can be effective however they can provide 100% prevention. Just like an umbrella's that is expected to keep you dry when it rains. Clearly you are better with an umbrella but you will still get wet.

A DLP tool can prevent staff that are using an expected path to remove information and that’s where the story ends.

Gaps and Holes



It is the unexpected where the damage can be performed. Most organisations also try to prevent unauthorised use of Dropbox, Google Drive and other similar tools. The logic is sound that by blocking access of these tools to their user group it will prevent files being sent outside of the firewall without permission.

The truth is that there are a multitude of tools that can provide such functionality and the static ‘black list’ is just not dynamic enough.

It is only when you go to some of the major Indian outsourcers that you see that disabled USB and smartphones with cameras are outlawed. For the most part, we see that iPhones and Samsung phones are everywhere – thus taking a simple photo of a screen of data is the way such sensitive information can literally walk out the door.

What about old fashion print copies? Yes, while printing is monitored we really don’t check suitcases for removal of documents.


Social Media analysis

There are clues that can be found from mining Linkedin, Facebook Activity etc to see correlate poor performers and what these staff are posting on social media. There are specialist companies that do amazing forensics to understand who is connected to who. This analysis can look back in history and see patterns even when friends and connections have been undone.

Taking a larger data set, not quite big data of negative social media posts along with poor performer ratings, absenteeism can give you some interesting insights.


Yes, you can predict your employees engagement and more specifically when employees are going to leave with corporate data.


http://www.cso.com.au/article/584128/how-do-know-when-an-employee-going-leave-all-your-corporate-data/

Friday, September 18, 2015

IT Security - “Failure to see” or Failure to Act?


From my experience it is often a failure and oversight that leads to a major issue. The major risks are usually in large enterprises well documented and even known - Why then is it that we don’t act?
Is this a failure to see? Perhaps a failure to act? Or worse still both failure to see and act?


Getting Numb

Many in IT Security have been on this gig for some years, it is not a place that one typically goes for a short period of time. It tends to attract a certain kind of IT Professional that has an interest and aptitude for this arena.

Very thick skin is required as there is always resistance from various IT parties and partners. My belief is that all this daily interchange starts to make the IT Security professional a little numb and accepting too much of risks on his\her own shoulders.

At other times, the role of the IT Security Manager is to raise risks and “cry wolf”, unfortunately while courage is a required attribute it soon runs out. As a diligent IT Security Manager you will have to go into battle often and how others respond to you has a real impact.

This is not about overt resistance but often the passive silence that can be just as unnerving.

Top down Thinking

I recall a story where I was the CIO and also Chief Privacy Officer for a $1B company and with my hybrid Business and IT team we had to tackle a number of behavioural issues.

The situation was:
1) less than 20% training compliance for IT Security and Privacy training. The approach was old school antiquated and there was no teeth to enforce.

2) We operated in 50 offices, and most of these did not comply with physical or logical security. As such PC’s were left logged on, passwords shared, laptops not locked away, desk drawers and printing  faxes left around, filing cabinets unlocked.


Gamification with Teeth

As we were in Japan, I could access some great game developers and we decided that we would start off with a complete overhaul of the training. All staff were told that this is now mandatory with an online verification and to pass they would have to complete a 10 minute game.

Red Pig, Yellow Pig and Green Pig – as you wandered around your office you had to comply with the policy to lock drawers, filing cabinets etc It was a simple game and actually a little fun.

The result we had 100% compliance even for our 1000 sales reps, who are always too busy to take the test, that this worked. While there was some level of threat and demand that the training be completed by a certain date, this was still quite an amiable level.

Once all staff were trained which was completed within two weeks. We then embarked on stage 2 – adding the teeth.

Pig Hunting

My team embarked on dawn raids across all our offices, still were unannounced and we walked the floors looking for non compliance to security. Where laptops were left out, drawers unlocked or office’s we entered and left a Red or Yellow Pig Sticker.

We also recorded the location of the offender against the floor plan. This was later shared in full detail at Exco with followup in the ensuring months. While the sticker idea looked ‘light’ it also carried with it a warning that a repeat offence would result in a HR Warning Letter.

As we had left no prisoners, even the CEO had left his office unlocked and his EA was not that happy.
We taught, we saw and we corrected

The success of the program was all about changing behavior and making it part of the culture what was acceptable and what wasn’t.

There was unambiguity and it was clear that within 6 months that were weren’t going to change. In fact we had agreed that we would start to get even more stringent.
For instance, the team started to check were the multifunction printer and scanner being flushed every day so that there was not sensitive data left behind.


Leadership is what matters

The engagement of the team into the activities was strong and they progressed from wondering why were they invited into this activity through to taking full ownership and accountability.

I never heard or witnessed any angry response from any of the non-compliant persons. They all understood from the ‘game’ what their responsibilities were and had to take this on the chin.

In the end this is about getting real ownership of security to where it matters. And that is with the staff who use systems and processes.

So where are you, do you have a failure to see? Or failure to act??


http://www.cso.com.au/article/576775/it-security-failure-see-failure-act/