Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Point to remember for CISA exam:
- CSA
- (1)In any given scenario, statistical sampling is to be used when the probability of error must be objectively quantified (i.e no subjectivity is involved).
- (2)In any given scenario, attribute sampling is best suitable for compliance testing
- (3)In any given scenario, best sampling technique where fraud is being suspected is Discovery Sampling.
- (4)A higher confidence coefficient will result in the use of a larger sample size. In other way, higher sample size will give higher confidence coefficient.
- (5)In any given scenario, when internal controls are strong, confidence coefficient /sample size may be lowered.
- (6)In any given scenario, statistical sampling minimizes the detection risk.
- Testing Concept-Online Auditing Techniques
- When audit trail is required- answer has to be snapshot.
- When early detection of error or irregularities is required- answer has to be audit hook.
- Best technique to identify transactions as per pre-defined criteria-answer has to be CIS.
- When fictitious entity is created in live production-answer has to be ITF.
- FIREWALS
- (1)Out of all types of firewall, Application-Level Firewall provides greatest security environment (as it works on application layer of OSI model).
- (2)Out of all types of firewall implementation structures, Screened Subnet Firewall (DMZ) provides greatest security environment (as it implements 2 packet filtering router and 1 bastion host).
- (3)In any given scenario, most robust configuration in firewall rule is ‘deny all traffic and allow specific traffic’ (as against ‘allow all traffic and deny specific traffic’).
- (4)In any given scenario, Stateful Inspection Firewall allows traffic from outside only if it is in response to traffic from internal hosts.
- (5)In any given scenario, following are the OSI layers at which various firewall operates:
- RTO/RPO
- (1) RTO of 2 hours indicates that organization needs to ensure that their system downtime should not exceed 2 hours.
- (2) RPO of 2 hours indicates that organization needs to ensure that their data loss should not exceed 2 hours of data captured.
- (3)In any given scenario, for critical systems, RTO is zero or near zero. Similarly, for critical data, RPO is zero or near zero.
- (4)In any given scenario, lower the RTO/RPO, higher the cost of maintenance of environment.
- (5)In any given scenario, low RTO/RPO indicates that disaster tolerance is low. Other way round, if disaster tolerance is low, RTO/RPO should be low.
- (6)In any given scenario, when RTO is low, mirrored site or hot site is recommended.
- (7)In any given scenario, when RPO is low, mirror imaging or real time replication for data back-up is recommended.
- (8)In any given scenario, where RPO is zero, synchronous data backup strategy to be used.
- (9)Both RTO & RPO are based on time parameters. The lower the time requirements, the higher the cost of recovery strategies.
- WIFI
- (1)In any given scenario, following are the best practises for Wireless (Wi-Fi) security:
- (a)Enable MAC (Media Access Control) address filtering.
- (b)Enable Encryption to protect data in transit.
- (c)Disable SSID (service set identifier) broadcasting.
- (d)Disable DHCP (Dynamic Host Configuration Protocol).
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement