Extremerisk


The Presentation inside:

Slide 0

Extremerisk 10 WAYS poorly managed tech Can destroy your company


Slide 1

dude, failing to manage IT risk is serious


Slide 2

you might have to stop doing business altogether stolen data can be used against your customers the press may have a field day on you it will be even worse in social media you could lose critical assets employees or directors could go to jail competitors may learn your secrets you may have to pay fines the trust you've built into your brand may disappear IT can be extremely complex & opaque, may require very specialized skills and changes very, very fast


Slide 3

and just cause you’re a small, nimble start-up does not give you license to be sloppy (especially if you hope to pass exit due diligence)


Slide 4

here are 10 obvious, but common, mistakes to avoid…


Slide 5

01 Lack leadership mistake


Slide 6

01 Lack leadership Leadership must understand the strategic importance of technology risk management They must also be involved with decision-making and communicate like crazy mistake


Slide 7

Lack leadership Leadership must put in place a technology risk management (TRM) framework that includes the right culture, policies, standards (enterprise requirements), & control procedures They must also be responsible for communications & the quality of firm wide execution 01 mistake


Slide 8

Lack leadership Leadership must get the right people, in the right roles, at the right time, with the right training 01 mistake


Slide 9

Lack leadership Leadership must ensure that risks are identified and prioritized by likelihood and severity 01 mistake


Slide 10

Lack leadership Leadership must identify control gaps, prioritize and budget for remediation, & monitor projects to close them 01 mistake


Slide 11

Lack leadership Leadership must approve & track exceptions 01 mistake


Slide 12

Lack leadership Line managers must be engaged & accountable for TRM TRM must not be seen as red tape. It must be seen as a core job function of a technology manager (and disciplined/rewarded as such) 01 mistake


Slide 13

02 Lack trm framework mistake


Slide 14

02 Lack trm framework A TRM Framework must protect data & IT assets from unauthorized access or disclosure, misuse, and fraudulent modification mistake


Slide 15

02 Lack trm framework A TRM Framework must ensure data confidentiality, system security, reliability, resiliency, & recoverability mistake


Slide 16

02 Lack trm framework A TRM Framework must define roles & responsibilities mistake


Slide 17

02 Lack trm framework A TRM Framework must identify & prioritize IT assets mistake


Slide 18

02 Lack trm framework A TRM Framework must identify & assess impact and likelihood of operational & emerging risk including internal & external networks, hardware, software, interfaces, operations, and human resources The firm must also have a mechanism to identify risk trends externally mistake


Slide 19

02 Lack trm framework A TRM Framework must methodically & regularly inventory and prioritize risks, controls, exceptions, and gaps mistake


Slide 20

02 Lack trm framework A TRM Framework must be updated regularly mistake


Slide 21

03 Lack partner oversight mistake


Slide 22

03 Lack partner oversight IT provided or supported by partners must be in scope & leadership must fully understand outsourcing risks Outsourced IT infrastructure is still part of your TRM. You can’t wash your hands of it * Provision or support includes system development and support, DC ops, network admin, BCP, hosting / cloud and can involve one or more parties in or out of country mistake


Slide 23

03 Lack partner oversight Proper due diligence must ensure viability, capability, reliability, & stability of vendors mistake


Slide 24

03 Lack partner oversight Written contracts must define expected risk-related service levels, roles, obligations, & control processes in detail They must also be reviewed regularly * For example, performance targets, service levels, availability, reliability, scalability, compliance, audit, security, contingency planning, disaster recovery and backup mistake


Slide 25

03 Lack partner oversight A Service Level Management Framework such as the IT Infrastructure Library (ITIL) must ensure continuing, monitored controls compliance mistake


Slide 26

03 Lack partner oversight An exit / backup plan must be in place to switch partners if required mistake


Slide 27

04 Lack portfolio management mistake


Slide 28

04 Lack portfolio mgmt The entire technology portfolio/platform must be managed through it's lifecycle The business must be engaged with portfolio strategy as a key stakeholder mistake


Slide 29

04 Lack portfolio mgmt Enterprise architecture strategy must be supported by accurate & accessible MIS and asset management data mistake


Slide 30

04 Lack portfolio mgmt Leadership must define, document, & communicate the target state platform mistake


Slide 31

04 Lack portfolio mgmt A professional Project / Change Management Framework like Project Management Body Of Knowledge (PMBOK) or ITIL must guide change from current to target mistake


Slide 32

04 Lack portfolio mgmt A professional Quality Management program should ensure quality of build and operate For example, a documented software development lifecycle (SDLC) should effectively guide development & code quality mistake


Slide 33

04 Lack portfolio mgmt There must be strong testing & code review controls mistake


Slide 34

04 Lack portfolio mgmt IT Acquisition must be strategically aligned mistake


Slide 35

04 Lack portfolio mgmt Technology exit planning must be explicit & tracked mistake


Slide 36

05 Lack service management mistake


Slide 37

05 Lack service mgmt Ongoing IT operations must be guided by a Service Management (SM) Framework like ITIL mistake


Slide 38

05 Lack service mgmt The SM Framework should cover: Change Management & DevOps Release & Deployment Management Capacity Management Incident Management Problem Management Source Code Control Asset Inventory & Config Management Backup & Recovery mistake


Slide 39

06 Lack recoverability mistake


Slide 40

06 Lack recoverability The firm needs a realistic, business-prioritized, strategically-aligned & simple business continuity plan (BCP) that ensures reliability, performance, scalability, availability, and recoverability mistake


Slide 41

06 Lack recoverability The BCP should identify critical systems (those that must not go down) as well as recovery point objectives (RPO) and recovery time objectives (RTO) to guide restoration service levels mistake


Slide 42

06 Lack recoverability The disaster recovery plan should cover multiple scenarios, expose dependencies, & be tested regularly mistake


Slide 43

06 Lack recoverability Backup management must ensure that IT assets can be recovered as soon as required, depending on priority & that dependencies are understood mistake


Slide 44

06 Lack recoverability There should be a Communications Plan defined in advance to deal with various scenarios mistake


Slide 45

07 Lack data security mistake


Slide 46

07 Lack data security You must protect data, hardware, software, and networks from accidental or intentional unauthorized access or tampering by internal or external parties mistake


Slide 47

07 Lack data security You must identify levels of data sensitivity and ensure escalating levels of protection based upon the significance / priority of risk. mistake


Slide 48

07 Lack data security You must have end-to-end data protection such as encryption when you are dealing with confidential data Your controls / standards must be in force wherever your data is stored or transmitted mistake


Slide 49

07 Lack data security You must properly dispose of assets that hold confidential data mistake


Slide 50

07 Lack data security You must have a mechanism to monitor security & react as required mistake


Slide 51

08 Lack system security mistake


Slide 52

08 Lack system security You must protect data, hardware, software, and networks from accidental or intentional unauthorized access or tampering by internal or external parties mistake


Slide 53

08 Lack system security You must identify levels of sensitivity & ensure escalating levels of protection based upon the significance / priority of risk mistake


Slide 54

08 Lack system security You must ensure that IT assets are patched as required You must ensure that IT assets are migrated out of production before End-of-Life or End-of-Service mistake


Slide 55

08 Lack system security You must deploy the right level of network security (including anti-virus) across operating systems, network devices, databases, and enterprise mobile devices mistake


Slide 56

08 Lack system security Key points in the infrastructure (perimeter & internal as required) must be protected through intrusion detection & prevention tools such as firewalls mistake


Slide 57

08 Lack system security You must test security using vulnerability assessment & penetration testing regularly mistake


Slide 58

08 Lack system security You must have a mechanism to monitor security and react as required mistake


Slide 59

09 Lack physical security mistake


Slide 60

09 Lack physical security You must protect data, hardware, software, and networks from accidental or intentional unauthorized access or tampering by internal or external parties mistake


Slide 61

09 Lack physical security You must identify levels of sensitivity & ensure escalating levels of protection based upon the significance / priority of risk mistake


Slide 62

09 Lack physical security There must be regular threat and vulnerability assessments mistake


Slide 63

09 Lack physical security You must implement appropriate physical security such as need-to-access-only requirements & security / surveillance systems mistake


Slide 64

09 Lack physical security Critical resources such as air, water, power fire suppression, & communications should be redundant where required mistake


Slide 65

10 Lack access controls mistake


Slide 66

10 Lack access controls For critical / sensitive systems an individual must not be granted access alone (never-alone principle) mistake


Slide 67

10 Lack access controls The transaction process should prevent a single person from initiating, approving, and executing by themselves (segregation of duties) Job rotation is recommended for sensitive functions mistake


Slide 68

10 Lack access controls Access should be limited to need-to-know (access-control principle) mistake


Slide 69

10 Lack access controls Access should be logged and access rights should be easy to review & modify as access rights change naturally over time mistake


Slide 70

10 Lack access controls There must be separate environments for development, testing, and production with controlled access to production where production access is limited and governed by segregation of duties mistake


Slide 71

SHARE THIS DECK & FOLLOW ME (please-oh-please-oh-please-oh-please) stay up to date with my future slideshare posts http://www.slideshare.net/selenasol/presentations https://twitter.com/eric_tachibana http://www.linkedin.com/pub/eric-tachibana/0/33/b53


Slide 72

CLICK HERE FOR MORE!!!!


Slide 73

CREATIVE COMMONS ATTRIBUTIONS & REFERENCES Title Slide: http://www.flickr.com/photos/[email protected]/ Dude Slide: http://www.flickr.com/photos/karen_od/ Ewok Slide: http://www.flickr.com/photos/daviddurantrejo/ Leadership Slide: http://www.flickr.com/photos/daviddurantrejo/ Tech Risk Mgmt Slide: http://www.flickr.com/photos/daviddurantrejo/ Partner Oversight Slide: http://www.flickr.com/photos/daviddurantrejo/ Service Mgmt Slide: http://www.flickr.com/photos/gageskidmore/ Portfolio Mgmt Slide: http://www.flickr.com/photos/fotomaf/ Recoverability Slide: http://www.flickr.com/photos/karen_od/ Data Security Slide: http://www.flickr.com/photos/daviddurantrejo/ System Security Slide: http://www.flickr.com/photos/daviddurantrejo / Physical Security Slide: http://www.flickr.com/photos/fotomaf/ Access Controls Slide: http://www.flickr.com/photos/daviddurantrejo/ http://www.mas.gov.sg http://www.isaca.org http://coso.org/guidance.htm http://www.itil-officialsite.com http://www.pmi.org Please note that all content & opinions expressed in this deck are my own and don’t necessarily represent the position of my current, or any previous, employers


×

HTML:





Ссылка: