Accelerating Secure SAP Application Delivery

© 2018 Delphix. All Rights Reserved. Private and Confidential.© 2018 Delphix. All Rights Reserved. Private and Confidential.
Accelerating Secure SAP
Application Delivery

© 2018 Delphix. All Rights Reserved. Private and Confidential.
Accelerating
Innovation
Mitigating Risk
Agenda

Accelerating Innovation

© 2017 Delphix. All Rights Reserved. Private and Confidential. 4
Key Challenges for SAP Teams
57
%
Expensive
Projects that run over
budget
Slow
Projects that run over
schedule
Low Quality
Projects achieving < 50% of
planned benefits
46
%
57
%
“Organizations that develop a data strategy are less
likely to experience issues that lead to extended
implementation durations.”*#1 reason for schedule
overages
Data Issues
*Source: 2016 Report on ERP Systems, Panorama
Consulting

Pitfalls of SAP System Copies
FOR NON-PRODUCTION ENVIRONMENTS
56% of companies run
system copies quarterly.
25%of companies run
system copies every 6 months.
30 daysfor making
coordinated system copies
across an SAP landscape.
100+steps in making a
single SAP system copy.
5-20 employees run an
average manual system copy.
5+ days to run or
manual system copy.
88% of all security breaches
involve insider negligence, says
Ponemon inst.
50% of cybersecurity pros
say databases are the most
vulnerable targets of insider
attacks.
*SNP Schneider-Neureither & Partner SE. Heidelberg 2018 69121 Heidelberg

SAP Data Management Today
PRODUCTION
APP
RDBMS or
HANA
1x TB
STORAGE
BUILD TEST DEV
NON-PRODUCTION
! Days or weeks to provision / refresh
3x TB of redundant storage!
! Downtime during refresh
Overhead in pre- and post-processing!
Legacy SAP Migration Tools

Leads to

Poor Data Quality in SDLC
Data
Quality
Trans1 Test
Cycle 1
✗ ✓
Test Cycle 1
✗
Trans
Fix
✓
Test
Cycle 2
✓
Test
Cycle 3
✗
Release
Readiness
Create Data Create Data Trans
Fix 3
✓
Create
Data
Release
Delayed..

Outdated and Non-Agile New Hire & Partner Onboarding
Environments
Non-secure and outdated SAP data based training environment

With Delphix

Data
Quality
Trans1 Test
Cycle 1
✗ ✓
Test
Cycle 1
✗
Trans
Fix
✓
Test
Cycle 2
✓
Test
Cycle 3
✗
Release
Readiness
Create
Data
Create
Data
Trans
Fix 3
✓
Create
Data
Release
Delayed..
Legacy Methods
Data
Quality
100%
0%
Trans1 Test
Cycle 1
✗ ✓
Trans 1
Fix
b1
✗
Trans
Fix 1
✓
Test
Cycle 2
✓
Test
Cycle 3
✓
(Rewind)
b1 b2 b3b0
✗
Trans
Fix 2
Test
Cycle 4
Test
Cycle 5
✓ ✓
Release
Readiness
b0 b2 b3
b2 b3
Ready for
Release!
Test with Production Quality Data for Entire SDLC

Initializ
eSAP Refresh
Faster SAP releases
Less waiting for data operations compresses development and testing cycles
Increase software quality
Maintaining high data quality reduces data-related defects
Deploy Transports
SAP Code and Config
Back to the bookmarked state
Run Tests
Cycle 1: Create, modify, test data
Cycles 2 … ∞: Create, modify, test same data
Create a Save Point
Bookmar
k
Save Point #2
Bookmar
k
Rewind
BUILD, TEST,
DEV
Dec 1VDB Creation Dec 2 Dec 3
SAP Landscape/Project
Manager
Accelerate SAP Application Development Test Cycles

BUILD
TEST
DEV
1 Ingest and mask data from Production
2 Create secure virtual copies
3 SAP Project/Environment Manager manages access and distribution
Perform SAP Post processing tasks on virtual copies4
Virtual copies are ready for use5
✔
Present to non-prod
Hosts
BDLS and post processing
Deploy Transports
SAP Code and Config
✔
Bookmark, open for
use
Feb 1 Feb 2
SAP Project /
Environment
Manager
Feb 1Mask data before it leaves Production
Developers,
Testers,
Consumers
Provide SAP Data as a Self-Service with Data Controls

Training
Sandbox
Regression
Active branch
Lower Complexity and Costs
Eliminate idle systems to reduce
maintenance complexity, plus
licensing, server, and storage
costs.
Increase Flexibility and Utilization
Environment “hoteling” with quick
context switching. Unique time flow
associated with each branch.
On-Demand SAP Data Environments for New Hire and Partner
Onboarding

PRODUCTION
APP
RDBMS or HANA
1x TB STORAGE
Training 1
1 One-time link and load
2 Mask data on premises, ensuring no sensitive data leaves the
production network
3 Up to 2/3rd data compression
NON-PRODUCTION
May 23
06:11
May 22
12:43
May 22
08:41
~0.3x TB STORAGE
Continuously record unique, incremental changes4
Mask data before it leaves
Production
Up to 2/3rd
Compression
Share data blocks instead of duplicating5
Reduce SAP Data Provisioning Time
Training 2 Training 3

Data Quality
Project Velocity
Increase Refresh
Current State Decrease Refresh
High
High
Low
Low
Eliminate impact to SAP teams with reset
instead of refresh
“Always-on Landscapes”
Maintain data quality in test environments
“Pristine data”
Streamlined data delivery and self-service
control
“Reduced Manual Effort”
Deliver high-quality
data at speed!
Eliminate the speed/quality tradeoff

Mitigating Risk In SAP Data

NON-PRODUCTION (80%)
PRODUCTION DATA (20%)
» Is constantly growing
» Entails multiple types of repositories
» Is often less protected by security and
governance measures
Non-Production Data:
Non-Production Data Represents a Major Hidden Risk

• Columns: Column names are semi- random German
codes – not allowing for sensitive data identification (Ex.
UMRD2).
• Application: High amount of referential integrity is done
at the application layer (not database).
• Speed: Almost all solutions go through APIs, which are
extremely slow.
Application Table Names
Column Names Compressed Tables
Why SAP Masking is Hard

Transparent
Pooled
Cluster
▪Used to store key data (lists of customers, email addresses, etc.)
▪Can be directly accessed using SQL
▪Can have 1 or more primary key
▪There is only a single table
▪Secure Data Distribution
▪Automated/Scheduled
90%
▪Mostly used to store system data but some key HR and FI data
▪Can not be read outside of SAP (APIs)
▪Group and store a large amount of small tables together
▪Used to store system data system data but some key HR and FI data
▪Can not be read outside of SAP (APIs)
▪Group and store a small number of large tables together
8%2%
The SAP Data Model (Types of Tables)

• Intelligent: Solution that can identify sensitive data and
know how to mask it. Feature: Pre-built accelerator pack
for standard SAP tables.
• Speed: High performance masking solution. Feature:
Database level masking for only transparent tables. No
support for pool/cluster.
• Referential Integrity: Referential integrity across
different database types and applications. Feature: Data
Source agnostic algorithms.
A high performance out of the box masking solution
that can work alongside masking of other data
sources.
Delphix SAP Masking

Mask Sensitive Data with Referential Integrity
“DATA AT
RISK” IS IN
DATABASES
Claimant Table
ID First_Name
1 George
2 Mary
3 John
Employee Table
ID First_Name
5 John
6 George
7 Mary
Claimant Table
ID First_Name
1 Romanth
2 Clara
3 Damien
Employee Table
ID First_Name
5 Damien
6 Romanth
7 Clara
UNMASKED DATA MASKED DATA
✓ REALISTIC
✓ REFERENTIAL INTEGRITY
✓ IRREVERSIBLE ✓ REPEATABLE
SENSITIVE DATA IN PRODUCTION
Personal Identification Numbers, Credit Card Information,
Patient Information, Email Addresses

• Back-office operations needed optimization to stay
competitive
• Planned migration of SAP apps to new data center
• System setup and refresh slowed testing, release
speed
• Migration plan called for long period of system
downtime
Agile Data Migration and Testing for
SAP
5 to 0 Days
of planned downtime for
migration
Synchronized Data
across 5 dependent SAP
systems to accelerate
integration testing
Fast Rewind
of SAP data to point-in-time
bookmarks

Zero Downtime Refresh
Steps:
1. Export settings from the Q01 SAP instance
2. Provision a fresh VDB on the Interim DB Server
3. Connect the SAP Interim App Server
4. Import settings from the Q01 SAP instance to the
Interim SAP Server
5. Perform post copy (post refresh) steps
6. Shut down both SAP App Servers
7. Shut down and drop the Q01 VDB
8. Shut down the Interim VDB
9. Migrate the Interim VDB to the Q01 Database
Server
10. Start up the new Q01 VDB
11. Start up the Q01 App Server
Note: Q01 continues to be usable at this time.
- This is the currently used application and database
- This is an available application and database
*Refresh Complete*

25
This is the currently used application and database
This is an available application and database
Delphix Engine
Prod Archive (dSource)
Primary
Database Server
Interim DB Server
Regular
SnapSync
(rman)
Prod
Q01
Q01
App Server Interim App Server

26
Steps:
Delphix Engine
Primary
Database Server
Q01
1
2
3
4
5
Export settings from the Q01 SAP instance
Provision a fresh VDB on the Interim DB Server
Connect the SAP Interim App Server
Import settings from the Q01 SAP instance to the
Interim SAP Server
Perform post copy (post refresh) steps
Note: Q01 continues to be usable
at this time.
Q01
SAP Settings
Q01 Q01
2
3
4
5
Interim DB Server

27
Steps:
Delphix Engine
Primary
Database Server
Interim DB Server
Q01
6 Shut down both SAP App Servers
7 Shut down and drop the Q01 VDB
8 Shut down the Interim VDB
9
Migrate the Interim VDB to the Q01 Database
Server
11 Start up the Q01 App Server
Q01
Q01 Q01
6
10 Start up the new Q01 VDB
107 8Q01
9
Q01Q01
Q01
11

28
Delphix Engine
Primary
Database Server
Interim DB Server
Q01 Q01
Q01 Q01
7 Q01Q01Q01
Q01
*Refresh Complete*

Thank You

Near Zero Downtime
3
0

Accelerating Secure SAP Application Delivery

Recommended

More Related Content

What's hot (20)

Similar to Accelerating Secure SAP Application Delivery (20)

More from Delphix (19)

Recently uploaded (20)

Accelerating Secure SAP Application Delivery