Monday, 25 February 2013

What is SAP ?


  1.  what is sap?
  2.     what are the advantages of sap ?
  3.      what are the disadvantages of sap?
  4.     SAP Componenet
  5.      sap versions


 2. sap 3-tier architecture.. 8
  1.    PRESENTATION LAYER
  2.    APPLICATION LAYER
  3.    DATABASE LAYER
1.    What is SAP?
  S=System A=Applications P=Product
  SAP is an Package and it is an ERP package
  SAP is the market and technology leader in Business management software, providing comprehensive business software through SAP applications services.

1.1 What are the advantages of SAP?
  SAP Advantages are Integration, Efficiency, Cost Reduction, Less Personal, and Accuracy.

  1.Integration

Integration can be the highest benefit of them all. The only real project aim for implementing ERP is reducing data redudancy and redudant data entry. If this is set as a goal, to automate inventory posting to G/L, then it might be a successful project. Those companies where integration is not so important or even dangerous, tend to have a hard time with ERP. ERP does not improve the individual efficiency of users, so if they expect it, it will be a big disappointment. ERP improves the cooperation of users.


  2.Efficiency
Generally, ERP software focuses on integration and tend to not care about the daily needs of people. I think individual efficiency can suffer by implementing ERP. the big question with ERP is whether the benefit of integration and cooperation can make up for the loss in personal efficiency or not.


§  3.CostReduction
It reduces cost only if the company took accounting and reporting seriously even before implementation and had put a lot of manual effort in it. If they didn't care about it, if they just did some simple accounting to fill mandatory statements and if internal reporting did not exists of has not been fincancially-oriented, then no cost is reduced.

§  4. Less personnel
Less reporting or accounting personnel, but more sales assistants etc.
§  5.Accuracy
No. People are accurate, not software. What ERP does is makes the lives of inaccurate people or organization a complete hell and maybe forces them to be accurate (which means hiring more people or distributing work better), or it falls.



1.2 What are the disadvantages of SAP?
§  1.Expensive

This entails software, hardware, implementation, consultants, training, etc. Or you can hire a programmer or two as an employee and only buy business consulting from an outside source, do all customization and end-user training inside. That can be cost-effective. 


It depends. SAP can be configured to almost anything. In Navision one can develop almost anything in days. Other software may not be flexible.

2.Notveryflexible

It depends. SAP can be configured to almost anything. In Navision one can develop almost anything in days. Other software may not be flexible.

1.3 SAP Components: SAP Basis and ABAP(Installed Automatically)
a.    XI
b.    BI
c.    FI
d.    CRM
e.    SRM
f.     SCM etc
1.4  SAP Versions: ECC 5.0/6.0/7.0

1.    SAP: 3-Tier Architecture
Ø  Presentation Layer: Logon Pad
Ø  Application Layer: SAP
Ø  Database Layer: Oracle

Presentation Layer: The presentation layer enables the user to interact with the relevant application. This interface is typically called the GUI (Graphical User Interface) and it is used to execute the application logic, utilizing the other layers in the combined infrastructure. SAP LOGON PAD is a Presentation Layer in system architecture.


Application Layer: Applications are executed in the application layer. SAP (SAP ECC6.0, 4.7) is an Application Layer in system architecture

Database Layer: Database layer is managed data processing. Oracle, SQL is database layer in system architecture. 

1.    How to create customize system in SAP Logon Pad?
§  Click on SAP Log on Pad
§  Click on User_Defined button
§  Provide Description, Application Server, System ID, System No. Click on Save.
§  Example: Creating IRB system in SAP.



1.    What is SAP Authorization?
§  An authorization is a permission to perform a certain action in the SAP System.
§  Authorizations are used to control access at the application level.. 
§  SAP Authorization concept is basically used for SAP Security 
§  Security: Security means protecting your data and your busines 
.§  Security: Information security is a top priority – for our enterprise solutions, and for your enterprise operations.

§  SU01, PFCG, SU53, SUIM, SU01D etc Transaction Codes normally using in SAP Authorization.
                          §  Transaction Code: Transaction code is a combination of multiple programs.
§  Is a combination/groups of programs. 
§  Some examples are:1.     SU01: User Maintaince2.     PFCG: Role Maintaince3.     SU53: Authorization Check4.     SM01: Lock/Unlock Tcode5.     SU24: Maintain Auth Object check under transaction6.     SU10: User Mass maintaince7.     SU01D: User Display


Field: Smallest unit against which a check should be run. It is a least granular element/data element to secure the data/information.

Authorizations: Authorizations are used to control access at the application level.

Authorization Object: Groups 1 to 10 authorization fields together. These fields are then          checked simultaneously.

Authorization Object Class: Logical grouping of authorization objects

Profile: Profiles is to provide Authorization based on provided Authorizations and Authorization Objects. We used to create profiles up to 4.6C version in SU02 Transaction Code, after 4.6C version these profiles will create automatically while modifying/creating roles or generation roles.

Role: Its is a combination of Menu’s, Authorizations, Profiles and personalization. A role is a group of activities performed within business scenarios. Or Activities assigned to the user. Or a role is a set of functions describing a specific work area. Roles consist of Menu, Authorizations, Organizational values.

Authorization Groups: The authorization group allows extended authorization protection for particular objects



Role Administration
PFCG: Creation of roles/profile generation.
Roles: Consists of transaction codes and authorization objects organisational values.
Options:
a.    Display Role
b.    Change Role
c.    Create Role
d.    Create Composite Role
e.    Copy Role
f.     Delete Role
g.    Transport Role
h.    Download Role
i.      Upload Role
j.      Mass_Download
k.    Mass_Transport
Display Role: Readable mode only
                                                      i.        Go to PFCG
                                                    ii.        Provide Role name in Role name field and click on Display button. You will get all the details about that role. It provides Description, Menu Tab, and Authorization User.
Create Role: Creation of Role.
                                                      i.        Go to PFCG
                                                    ii.        Provide Role name and click on create button.(You will see Red colour icon that means we have to fulfil all that information)
                                                   iii.        Provide description and long text.
                                                   iv.        In Menu Tab: Create folder and add transaction code in that folder.(Eg: SU01D)
                                                    v.        In Authorizations Tab:
a)    Click on Authorization Tab.
b)    Will ask for save the changes. Click on save.
c)    As per SAM document we have to provide organisational level in authorization object values. Save it. Execute now.
d)    Click on Generate Authorization Profile. Profile will generate automatically.
 Create Role: This is in editable mode.
                                                          i.    Go to PFCG
                                                        ii.    Provide role name which we want to modify and click on change role icon
                                                       iii.    Now, we are able to change description of role and long text of the role in Menu tab. We can create a folder also and able to add transaction code in that folder.
                                                       iv.    In Authorization Tab: we have to generate new profile for each modification.
Delete Role: Deletion of role from system. Just provide Role Name and click on Delete icon. It will delete from system.
Copy Role: Copy a old role information from old role
a)    Go to PFCG
b)    Provide role name and click on Copy role icon.
c)    It will ask from role to role.(From Role to Existing role).
d)    To Role=> New Role=> Copy all/Copy selectively.
e)    Once you done with copied part then click on change role.
f)     During copy of role menus and description copied from old in to the new role and also it copy authorization objects and organisational level. We have to generate new profile for this role because profile is never copy.
Create Composite Role: Two or more roles is nothing but composite
a)    Go to PFCG
b)    Provide role name and click on composite role
c)    Provide description as well as long text.
d)    Tab which are available in this role are Roles, Menu, User, Personalisation. (Note: Authorizations tab is absent in this role)
e)    Composite: Two or more single role. Provide single role in roles tab. Move to menu tab and click on Save.
f)     In Menu Tab: we can create new folder.
Transport Role:  Go to PFCG
a)    Provide role name
b)    Click on Transport role
c)    Click on check box(also transport generated profiles for single roles)
d)    Click on Execute. Click on continue. Again continue.
e)    Create Request(click on)(will prompt for customer requirement)
f)     Provide description for Transport Request(TR)
g)    Click on save and continue. TR will generate automatically.
h)   This is using for only one role.
Mass Transport:
a)    Go to PFCG
b)    PFCG=>Utilities=>Mass_Transport
c)    Click on Multiple selection
d)    Will ask for single values and same provide
e)    Click on execute. Again click on execute. Click on continue.
f)     Create request
g)    Provide description for TR
h)   Click on save and continue
i)     One TR will generate for multiple roles.
Download Role:
a)    Go to PFCG
b)    Provide role name
c)    Role=>Download
d)    Click on continue. Save as(save at machine)
e)    Click on save. You will get action performed successfully.
f)     Message: you successfully download role
g)    Other than profile everything is same in downloaded role



Mass Download Role:
a)    Go to PFCG
b)    Utilities menu in menu bar=>Mass_Download
c)    Click on multiple selection
d)    Provide roles for downloading
e)    Click on copy then execute
f)     Click on continue=>Save As=>provide file name and click on save=>continue.
Upload Role:
a)    Go to PFCG
b)    Role=>Upload
c)    Click on continue.
d)    Open(select file name from system)
e)    Click on open and then continue. If role is already exists then they will ask for override.
f)     NOTE: while uploading ticket in SAP we have to regenerate the profile in Authorization tab and save it.




Mass Upload Role:

a)    Go to PFCG
b)    Role=> Upload


User Types


1.    Dialog: Communicate to the system interactively.

2.    System: Background procession user. It is used in within system.
Dialog logon is not possible. No Human User.

3.    Communications: Dialog logon is not possible. Use a user type communication without dialog between systems.

4.    Service: Used as a dialog user. Dialog logon is possible. A User type of service is a dialog user that is available to an anonymous larger group of users/ multiple logon allowed. During the logon the system does not check initial password.

5.    Reference: Like the service user. A reference user is a general user not assigned to a particular person.
   
 
 Authorization Check:
The checking of authorizations in an SAP system. There are essentially two checks, The first check is performed by the system when transactions are called, and the second is then performed by checks in program.

SU53 transaction code is using for Authorization check.
a)    Go to SU53b)    Able to see Authorization check failedc)    Able to see all authorizations given to that user.d)    To overcome this we have to find another transaction code with proper permission from L3 and assigned that role to that user.e)    Use SUIM transaction code for help.  




















Thursday, 21 February 2013

Controlling Access to Information and Functions


Controlling Access to Information and Functions

Objectives :

Controlling Access

Access Control Attacks

Testing Access Controls

Identification and Authentication:

Identification: unproven assertion of identity

“My name is…”

  Userid

  Authentication: proven assertion of identity

   Userid and password

    Userid and PIN

     Biometric

Authentication Methods:

What the user knows

Userid and password

 Userid an PIN

What the user has

 Smart card

 Token

What the user is

  Biometrics (fingerprint, handwriting, voice, etc.)

How Information Systems Authenticate Users:

Request userid and password

 Hash password

Retrieve stored 
userid and hashed password

 Compare

Make a function call to a network based authentication service

How a User Should Treat Userids and Passwords:

Keep a secret

Do not share with others

Do not leave written down where someone else can find it

Store in an encrypted file or vault

 Use RofoForm

How a System Stores Userids and Passwords:

Typically stored in a database table

 Application database or authentication database

 Userid stored in plaintext

Facilitates lookups by others

   Password stored encrypted or hashed

If encrypted, can be retrieved under certain conditions

“Forgot password” function, application emails to user
If hashed, cannot be retrieved under any circumstance (best method)

Password Hashes:

Cain, Cracker top tab, right-click empty space, Add to List

LM hash is weak, no longer used in Win 7

NT hash is stronger, but not salted

Strong Authentication:

Traditional userid + password authentication has known weaknesses

 Easily guessed passwords

 Disclosed or shared passwords

Stronger types of authentication available, usually referred to as “strong authentication”

 Token

Certificate

Biometrics

Two Factor Authentication:

First factor: what user knows

Second factor: what user has

                        Password token

                        USB key

                        Digital certificate

                        Smart card

Without the second factor, user cannot log in

                        Defeats password guessing / cracking


Biometric Authentication:

Stronger than userid + password

Stronger than two-factor?

                        Can be hacked

Measures a part of user’s body

                        Fingerprint

                        Iris scan

                        Signature

                        Voice


Authentication Issues:

Password quality

Consistency of user credentials across multiple environments

Too many userids and passwords

Handling password resets

Dealing with compromised passwords

Staff terminations

Access Control Technologies:

Centralized management of access controls

                        LDAP

Active Directory, Microsoft's LDAP

                        RADIUS

Diameter, upgrade of RADIUS

                        TACACS

Replaced by TACACS+ and RADIUS

                        Kerberos

Uses Tickets

Single Sign-On (SSO):

Authenticate once, access many information systems without having to re-authenticate into each

Centralized session management

Often the “holy grail” for identity management

                        Harder in practice to achieve – integration issues

Reduced Sign-On:

Like single sign-on (SSO), single credential for many systems

But… no inter-system session management

User must log into each system separately, but they all use the same userid and password

Weakness of SSO and RSO:

Weakness: intruder can access all systems if password is compromised

Best to combine with two-factor / strong authentication

Access Control Attacks:

Intruders will try to defeat, bypass, or trick access controls in order to reach their target

Attack objectives:

                        Guess credentials

                        Malfunction of access controls

                        Bypass access controls

                        Replay known good logins

                        Trick people into giving up credentials

Buffer Overflow:

Cause malfunction in a way that permits illicit access

Send more data than application was designed to handle properly

                        “Excess” data corrupts application memory

                        Execution of arbitrary code

                        Malfunction

Countermeasure: “safe” coding that limits length of input data; filter input data to remove unsafe characters


Script Injection:

Insertion of scripting language characters into application input fields

                        Execute script on server side

SQL injection – obtain data from application database

                        Execute script on client side – trick user or browser

Cross site scripting

Cross site request forgery

Countermeasures: strip “unsafe” characters from input

Data Remanence:

Literally: data that remains after it has been “deleted”

Examples

                        Deleted hard drive files

                        Data in file system “slack space”

                        Erased files

                        Reformatted hard drive

                        Discarded / lost media: USB keys, backup tapes, CDs

Countermeasures: improve media physical controls

Denial of Service (DoS):

Actions that cause target system to fail, thereby denying service to legitimate users

                        Specially crafted input that causes application malfunction

                        Large volume of input that floods application

Distributed Denial of Service (DDoS)

                        Large volume of input from many (hundreds, thousands) of sources

Countermeasures: input filters, patches, high capacity

                         

Dumpster Diving:

Literally, going through company trash in the hopes that sensitive printed documents were discarded that can be retrieved

                        Personnel reports, financial records

                        E-mail addresses

                        Trade secrets

                        Technical architecture

Countermeasures: on-site shredding

Eavesdropping:

Interception of data transmissions

                        Login credentials

                        Sensitive information

Methods

                        Network sniffing (maybe from a compromised system)

                        Wireless network sniffing

Countermeasures: encryption, stronger encryption

Emanations:

Electromagnetic radiation that emanates from computer equipment

                        Network cabling

More prevalent in networks with coaxial cabling

                        CRT monitors

                        Wi-Fi networks

Countermeasures: shielding, twisted pair network cable, LCD monitors, lower power or eliminate Wi-Fi


Spoofing and Masquerading:

Specially crafted network packets that contain forged address of origin

                        TCP/IP protocol permits forged MAC and IP address

                        SMTP protocol permits forged e-mail “From” address

Countermeasures: router / firewall configuration to drop forged packets, judicious use of e-mail for signaling or data transfer

Social Engineering:

Tricking people into giving out sensitive information by making them think they are helping someone

Methods

                        In person

                        By phone

Schemes

                        Log-in, remote access, building entrance help

Countermeasures: security awareness training

Phishing:

Incoming, fraudulent e-mail messages designed to give the appearance of origin from a legitimate institution

                        “Bank security breach”

                        “Tax refund”

                        “Irish sweepstakes”

Tricks user into providing sensitive data via a forged web site (common) or return e-mail (less common)

Countermeasure: security awareness training

Pharming:

Redirection of traffic to a forged website

                        Attack of DNS server (poison cache, other attacks)

                        Attack of “hosts” file on client system

                        Often, a phishing e-mail to lure user to forged website

                        Forged website has appearance of the real thing

Countermeasures: user awareness training, patches, better controls

Password Guessing:

Trying likely passwords to log in as a specific user

                        Common words

                        Spouse / partner / pet name

                        Significant dates / places

Countermeasures: strong, complex passwords, aggressive password policy, lockout policy

Password Cracking:

Obtain / retrieve hashed passwords from target

Run password cracking program

                        Runs on attacker’s system – no one will notice

Attacker logs in to target system using cracked passwords

Countermeasures: frequent password changes, controls on hashed password files, salting hash

Malicious Code:

Viruses, worms, Trojan horses, spyware, key logger

Harvest data or cause system malfunction

Countermeasures: anti-virus, anti-spyware, security awareness training