Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Subjects : certifications, csslp, it-skills

Instructions:

Answer 50 questions in 30 minutes.
If you are not ready to take this test, you can study here.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.

1. Least privilege
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
Periodic publication by OWASP for top 10 Web application security vulnerabilites

2. Properties of secure software
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied

3. ISO /IEC 27000:2009
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Access request by a subject to an object is mediated each time and every time.
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy

4. Common best practices significant to Sofware Security
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.
OWASP - ITIL
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c

5. ISO/IEC 9216
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities

6. Security Controls
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges

7. ISO/IEC 27001:2005
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges

8. Single Loss Expectancy (SLE)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
OWASP - ITIL
Covers the necessary procedures and tools to validate software assurance
Provides a common glossary of terms and definitions - Overview and introduction to the ISMS family of standards that covered: Requirement definitions - Detailed guidance of PDCA process - Sector Specific guidelines and conformity assessement for ISMS

9. PCI DSS
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Concepts aim at mitigating disclosure - alteration - and destruction threats. These are supporting concepts to the core security objectives of CIA
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

10. Security design principles
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Secure applicatios running on secure hosts (systems) in a secure network
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

11. Configurations Parameters Management
Manual that provides understanding on how to detect Web application vulnerabilities in code review and what safeguards can be taken to address them
Predetermined number of user error allowed before recording it as a security violation
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Guidelines for quality software products - Six external quality characteristics to measure quality of software: functionality - reliability - usability - efficiency - maintainability - portability

12. OWASP development guide
Comprehensive guides for degining - developing and deploying secure Web applications and Web Services - Intended audiences are architects - developers - consultant - and auditors
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
SP800-12 : Introduction to computer security handbook - SP800-14: Generally accepted principles and practices for securing IT systems - SP800-30: Risk Management Guide for IT - SP800-64: Security Considerations in the information systems development
Access request by a subject to an object is mediated each time and every time.

13. EALs levels
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Periodic publication by OWASP for top 10 Web application security vulnerabilites

14. Flaw Hypothesis Method (FHM)
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Access request by a subject to an object is mediated each time and every time.
The likelihood that a threat can result into an incident. This is the overall risk of a system

15. STRIDE
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Support for accreditation and certification bodies that audit and certify ISMS
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy

16. FIPS140-2 (Security requirement for cryptographic modules)
Confidentiality - Integrity - Availability
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible
Iron triangle constraint (schedule - scope - budget) - Security as an afterthought - Security versus usability
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

17. Management Controls
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:

18. Vulnerability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Still under development - aimsto address ISMS implementation guidance
Provides Common Criteria to evaluate IT security product
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy

19. Popular guides developed by OWASP
Development guide - Code Review Guide - Testing Guide
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Microsoft Methodologies of Risk Management and it comprised the following steps: Assessment of assets - security risks

20. OCTAVE
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans

21. Session Management
Protection against unauthorized information disclosure. It helps maintaining privacy
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Security controls applied after a threat has been materialized
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable

22. FIPS 201
Successful completion of a critical task is dependent on 2 or more conditions that need to be met
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable

23. Benefits of coding standards
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

24. Clipping level
Predetermined number of user error allowed before recording it as a security violation
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system

25. OWASP Top 10
Periodic publication by OWASP for top 10 Web application security vulnerabilites
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent
Access request by a subject to an object is mediated each time and every time.

26. Authentication
Security functionality is easy to use and transparent
A weakness or flaw that could be accidentally triggered or intentionally exploited by an attacker - resulting in the breach or breakdown of the security policy
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
Covers the necessary procedures and tools to validate software assurance

27. Risk management process
Balancing act between the protection of IT assets and the cost of implementing software security controls so that the risk is handled approprietely. It includes: Preliminary assessement for the need of security controls - Identification of security c
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges

28. Vulnerabilities repositories
Specifies the requirements for establishing - implementing - operating - monitoring - reviewing - maintaining and improving a documented ISMS
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual

29. Holistic Security in software
Secure applicatios running on secure hosts (systems) in a secure network
Support policies at a granular and specific level - Can be characterized as internal and external
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors

30. Develop hack resilient software
Requires the incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC
Provides Common Criteria to evaluate IT security product
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
Risk remains after the implementation of mitigating security controls

31. Accountability
Ability to determine the actions and behaviors of a single individual within a system and to identify that particular individual
Number of incidents that can be expected in a year
Threat modeling methodology performed in the design phase of software development - Categories of threats: Spoofing - Tampering - Repudiation - Information Disclosure - Denial of Service - Elevation of privileges
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

32. OWASP testing guide
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Indicator of magnitude risk in a year ALE = SLE * ARO
Protection against unauthorized information disclosure. It helps maintaining privacy
Covers the necessary procedures and tools to validate software assurance

33. Challenges in implementing auditing/logging
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Performance impact - Information Overload - Capacity impact - Configuration Interfaces protection - Audit log protection
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Risk based information security strategy assessment methodology - developed by SEI in conjunction of US-CERT - Performed in 3 phases: Build asset based threat profile - Identify infrastructure vulnerabilities - develop security strategy and plans

34. Complete mediation
Covers the necessary procedures and tools to validate software assurance
Confidentiality - Integrity - Availability
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Access request by a subject to an object is mediated each time and every time.

35. ISO/IEC 27005:2008
Likely to be replaced by ISO/IEC 30001 under development - Provides standards for IS risk Management
Number of incidents that can be expected in a year
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Protection against unauthorized information disclosure. It helps maintaining privacy

36. Open design
Concept aims at ensuring that the appropriate levels of protection are provided to secure configurable parameters that are needed for the software to run
Use directed graph to specify the rights that a subject can transfer to an object or that a subject can take from another subject
Support DAC - Subject's capabilities are defined by the triple (object - rights and random numbers) - Random number in the triple is used to prevent a replay or spoofing of the triple's source - Column of the access matrix are called ACLs - Rows are
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software

37. DREAD
Specifies the architecture and technical requirements for a common identified standard for federal employee and contractors
Functionally tested - Structurally tested - Methodically tested and checked - Methodically designed - tested and reviewed - Semiformally designed - and tested - Semiformally verified design and tested - Formally verified designed and tested
A set of comprehensive requirements aimed at protecting payment account data security - 12 foundational requirements mapped into 6 control objectives - Requirement 6 and its subrequirements are directly related to software security - develop and main
Risk calculation and rating methodology that are often used with STRIDE - Rating performed accross 5 dimensions: Damage potential - Reproducibility - Exploitability - Affected users - Discoverability

38. ISO/IEC 27002:2005
Preventive Controls: Detection Controls: e.g background checks - periodic review of security controls - Recovery controls:
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS
Implementation detail of the design is independent of the design itself. Reviewing the design itself will not result in the compromise of the sageguards of the software

39. Auditing
Passive detective control - security concepts in which critical and business transactions are logged to build a history of events to be used in troubleshooting and forensic evidence - At a minimum - audit fields should include who - where - when - a
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Development guide - Code Review Guide - Testing Guide
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.

40. Technical Controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Security concept aims at: identity of an entity (person or resource) is specified in the format that the software is expecting it - Validates or verifies the identity information that has been supplied
The incorporation of security concept in the requirements - design - code - release - and disposal phases of the SDLC - include: - Confidentiality - integrity - availability - authentication - authorization - auditing - Session management - Error/exc
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable

41. Examples of Security Standards
Secure applicatios running on secure hosts (systems) in a secure network
OWASP - ITIL
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Coding Standards (internal) - PCI DSS - NIST Standards - ISO Standards - Federal Information Processing Standards

42. ISO/IEC 21827:2008
US-CERT Vulnerability Notes - Common Vulnerability Scoring System (CVSS) - Open Source Vulnerability Database - Common Vulnerabilities and exposure (CVE) - Common Weakness Enumeration (CWE)
SSE - CMM De-facto standard metric for evaluating security engineering practices for the organization or customer
Secure applicatios running on secure hosts (systems) in a secure network
Replacement of ISO 17799 standards - Provide guidelines for effective security management practices - Outlines control objectives and controls in diverse areas of ISMS

43. Economy of mechanism
Keep it simple principle to reduce the attack surface. Number of vulnerabilites increase with the complexity of the software design and code
The likelihood that a threat can result into an incident. This is the overall risk of a system
Entity should have the minimum access level access right to do the jo- The right is given for a minimum amount of time necessary to complete the job
OWASP - ITIL

44. Non Repudiation
Addresses the deniability of actions taken by either a user or the software on behalf of the user - Can be accomplished by auditing access information
A possibility that an unwanted - unintended - or harmful event may occur and resulted in an incident. The source can be a vulnerability.
Provides Common Criteria to evaluate IT security product
Specified requirements for a cryptographic module for 4 increasing qualitative level (1-4) intended to cover a wide range of potential application and environment

45. Authorization
Aims at controlling the access of a subject to an object based on rights and privileges granted to the requestor by the owner of the data or system - or according to a policy - Layered on top authentication and must not precede authentication unless
Mechanisms by which threats to software and systems can be mitigated. These mechanisms may be technical - administrative or physical. Improper implementation of these mechanism may become a threat to the system
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
Dependability - Trustworthiness : MInimum number or no vulnerabilities - Resilience : Resistant or tolerant of attacks and able to recover quickly with as little harm as possible

46. Availability
Software or data it processed must be accessible by only those who are authorized - It must be accessible only at the time that it is required.
Uses comprehensive penetration testing to test the strength of the security software in order to predict and analyze vulnerabilities
Predetermined number of user error allowed before recording it as a security violation
Number of incidents that can be expected in a year

47. Exposure factor (EF)
Consistency in style - Maintainability - Less prone to error and exposure when security is taken into consideration in the standards
Security Concepts that need to be considered when designing and architecting software: Least privilege - Compartmentalization (separation of duties) - Defense in depth - Fail Secure - Keep it simple - Complete mediation - Open Design - Least common m
Is recommended for validating access to system containing sensitive or critical information (FFIEC guidance on authentication)
Opportunity for a threat to cause loss. It plays an important role in the computation of risk.

48. Counter measures
Risk remains after the implementation of mitigating security controls
Supporting Controls: Identification - crptographic key management - security administration - system protections - Preventive Controls: authentication - authorization - access control enforcement - non repudiation - Detection and recovering controls:
Disallow the sharing of mechaniss that are common to more than one user or process with different levels of privilege
Security controls applied after a threat has been materialized

49. Core Security Concept
estimate potential loss of a single incident: SLE = Asset value * EF(%)
Security controls applied to mitigate a threat before it materializes
Confidentiality - Integrity - Availability
Protection against improper data alteration. It is a measure of software resiliency and pertains to the modification of data and the reliable function of the software - Data is internally and externally consistent

50. Information Security Models
Specifies at a high level the 'what' and 'why' for security - Provides the framework and point of reference that can be used to measure an organization's posture - requires support of executive management to be effective and enforceable
Access Control Models - Access Matrix - Take-Grant - BLP (Bell La-Padula) - State machine - Integrity Models - Biba Model - Clark-Wilson Model - Information Flow Models - Non-Interference - Chinese Wall (Brewer and Nash) model
Concept aims at ensuring that unintended and unreliable behavior of the software is explicitly handled - while maintaining a secure state and protection against CIA threats - Errors and exception messages should be non verbose and explicit - Software
Aims at mitigating session hijacking (MITM attack). Requires that session token is unique and that user session is tracked to detect and prevent session hijacking

Search BasicVersity Tests

Browse BasicVersity

3d Computer Modeling
Study | Quiz | Subjects: it-skills, multimedia | Questions: 150+
Actionscript
Study | Quiz | Subjects: it-skills, multimedia | Questions: 10+
Adobe Flash
Study | Quiz | Subjects: it-skills, multimedia, flash | Questions: 50+
Adobe Illustrator
Study | Quiz | Subjects: it-skills, multimedia | Questions: 100+
Adobe Illustrator Shortcuts
Study | Quiz | Subject: it-skills | Questions: 50+
Adobe Indesign Publishing
Study | Quiz | Subject: it-skills | Questions: 150+
Adobe Photoshop CS 2 - CS 3
Study | Quiz | Subject: it-skills | Questions: 70+
Adobe Photoshop CS 5
Study | Quiz | Subject: it-skills | Questions: 140+
Adobe Photoshop CS 5 Keyboard Shortcuts
Study | Quiz | Subject: it-skills | Questions: 170+
Adobe Photoshop Graphic Design
Study | Quiz | Subject: it-skills | Questions: 100+
Adobe Photoshop Tools And Commands
Study | Quiz | Subject: it-skills | Questions: 110+
Adobe Premiere Keyboard Shortcuts
Study | Quiz | Subject: it-skills | Questions: 50+
Adobe Premiere Pro
Study | Quiz | Subject: it-skills | Questions: 50+
After Effects Keyboard Shortcuts
Study | Quiz | Subject: it-skills | Questions: 170+
Agile Development
Study | Quiz | Subject: it-skills | Questions: 50+
Agile Scrum Methodology
Study | Quiz | Subject: it-skills | Questions: 10+
Ajax
Study | Quiz | Subject: it-skills | Questions: 30+
Android Programming
Study | Quiz | Subject: it-skills | Questions: 130+
Animation
Study | Quiz | Subject: it-skills | Questions: 60+
Asp.net Programming
Study | Quiz | Subject: it-skills | Questions: 100+

1 of 109 pages [Next] [Last Page]

Test your basic knowledge |

CSSLP: Certified Secure Software Lifecycle Professional

Search BasicVersity Tests

Browse BasicVersity

3d Computer Modeling

Actionscript

Adobe Flash

Adobe Illustrator

Adobe Illustrator Shortcuts

Adobe Indesign Publishing

Adobe Photoshop CS 2 - CS 3

Adobe Photoshop CS 5

Adobe Photoshop CS 5 Keyboard Shortcuts

Adobe Photoshop Graphic Design

Adobe Photoshop Tools And Commands

Adobe Premiere Keyboard Shortcuts

Adobe Premiere Pro

After Effects Keyboard Shortcuts

Agile Development

Agile Scrum Methodology

Ajax

Android Programming

Animation

Asp.net Programming