The document discusses verification and validation processes in information security. It defines verification as evaluating whether a product complies with regulations and specifications, while validation establishes evidence that a product achieves its intended requirements. Various verification and validation techniques are mentioned, including documentation review, functional testing, vulnerability analysis, and penetration testing. Levels of evaluation assurance from standards like the Common Criteria and methods from the NIST security testing methodology are also summarized.
AUTOMATED PENETRATION TESTING: AN OVERVIEWcscpconf
The using of information technology resources is rapidly increasing in organizations,
businesses, and even governments, that led to arise various attacks, and vulnerabilities in the
field. All resources make it a must to do frequently a penetration test (PT) for the environment
and see what can the attacker gain and what is the current environment's vulnerabilities. This
paper reviews some of the automated penetration testing techniques and presents its
enhancement over the traditional manual approaches. To the best of our knowledge, it is the
first research that takes into consideration the concept of penetration testing and the standards
in the area.This research tackles the comparison between the manual and automated
penetration testing, the main tools used in penetration testing. Additionally, compares between
some methodologies used to build an automated penetration testing platform.
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
This is chapter 4 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
EdgarDB - the simple, powerful database for scientific researchMark Khoury
Learn about proper data management for scientific research.
EdgarDB was designed and refined quite literally "in the lab". The research lab.
For anyone doing fundamental research, this is a game-changer.
This presentation identifies a way to use Risk Management to determine the extent and scope of a validation project, including what validation documents are needed and what should be tested. One validation size does not fit all validation projects! Using the Quality/Regulatory Risk and Functionality/Distribution Risk identifies an Overall System Risk. The Overall System Risk and the Type of System Change determine the needed Validation documents. A methodology to identify the extent of validation test scripts is discussed too.
AUTOMATED PENETRATION TESTING: AN OVERVIEWcscpconf
The using of information technology resources is rapidly increasing in organizations,
businesses, and even governments, that led to arise various attacks, and vulnerabilities in the
field. All resources make it a must to do frequently a penetration test (PT) for the environment
and see what can the attacker gain and what is the current environment's vulnerabilities. This
paper reviews some of the automated penetration testing techniques and presents its
enhancement over the traditional manual approaches. To the best of our knowledge, it is the
first research that takes into consideration the concept of penetration testing and the standards
in the area.This research tackles the comparison between the manual and automated
penetration testing, the main tools used in penetration testing. Additionally, compares between
some methodologies used to build an automated penetration testing platform.
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
This is chapter 4 of ISTQB Advance Technical Test Analyst certification. This presentation helps aspirants understand and prepare the content of the certification.
EdgarDB - the simple, powerful database for scientific researchMark Khoury
Learn about proper data management for scientific research.
EdgarDB was designed and refined quite literally "in the lab". The research lab.
For anyone doing fundamental research, this is a game-changer.
This presentation identifies a way to use Risk Management to determine the extent and scope of a validation project, including what validation documents are needed and what should be tested. One validation size does not fit all validation projects! Using the Quality/Regulatory Risk and Functionality/Distribution Risk identifies an Overall System Risk. The Overall System Risk and the Type of System Change determine the needed Validation documents. A methodology to identify the extent of validation test scripts is discussed too.
Chapter 1 - Introduction and Objectives for Test AutomationNeeraj Kumar Singh
This is the chapter 1 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
This is chapter 4 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Software Quality Analysis Using Mutation Testing SchemeEditor IJMTER
The software test coverage is used measure the safety measures. The safety critical analysis is
carried out for the source code designed in Java language. Testing provides a primary means for
assuring software in safety-critical systems. To demonstrate, particularly to a certification authority, that
sufficient testing has been performed, it is necessary to achieve the test coverage levels recommended or
mandated by safety standards and industry guidelines. Mutation testing provides an alternative or
complementary method of measuring test sufficiency, but has not been widely adopted in the safetycritical industry. The system provides an empirical evaluation of the application of mutation testing to
airborne software systems which have already satisfied the coverage requirements for certification.
The system mutation testing to safety-critical software developed using high-integrity subsets of
C and Ada, identify the most effective mutant types and analyze the root causes of failures in test cases.
Mutation testing could be effective where traditional structural coverage analysis and manual peer
review have failed. They also show that several testing issues have origins beyond the test activity and
this suggests improvements to the requirements definition and coding process. The system also
examines the relationship between program characteristics and mutation survival and considers how
program size can provide a means for targeting test areas most likely to have dormant faults. Industry
feedback is also provided, particularly on how mutation testing can be integrated into a typical
verification life cycle of airborne software. The system also covers the safety and criticality levels of
Java source code.
AN EFFECTIVE VERIFICATION AND VALIDATION STRATEGY FOR SAFETY-CRITICAL EMBEDDE...IJSEA
This paper presents the best practices to carry out the verification and validation (V&V) for a safetycritical
embedded system, part of a larger system-of-systems. The paper talks about the effectiveness of this
strategy from performance and time schedule requirement of a project. The best practices employed for the
V &Vis a modification of the conventional V&V approach. The proposed approach is iterative which
introduces new testing methodologies apart from the conventional testing methodologies, an effective way
of implementing the phases of the V&V and also analyzing the V&V results. The new testing methodologies
include the random and non-real time testing apart from the static and dynamic tests. The process phases
are logically carried out in parallel and credit of the results of the different phases are taken to ensure that
the embedded system that goes for the field testing is bug free. The paper also demonstrates the iterative
qualities of the process where the iterations successively find faults in the embedded system and executing
the process within a stipulated time frame, thus maintaining the required reliability of the system. This
approach is implemented in the most critical applications —-aerospace application where safety of the
system cannot be compromised
ICA provide vocational training courses under skill development initative on prescribed by DGET, GOVT.OF INDIA. This training is fully equipped to provide the candidates with the opportunity to develop through understandings of the taxation for individuals, companies, partnerships and other structures in India.
Chapter 1 - Introduction and Objectives for Test AutomationNeeraj Kumar Singh
This is the chapter 1 of ISTQB Advance Test Automation Engineer certification. This presentation helps aspirants understand and prepare content of certification.
This is chapter 4 of ISTQB Specialist Performance Tester certification. This presentation helps aspirants understand and prepare the content of the certification.
Software Quality Analysis Using Mutation Testing SchemeEditor IJMTER
The software test coverage is used measure the safety measures. The safety critical analysis is
carried out for the source code designed in Java language. Testing provides a primary means for
assuring software in safety-critical systems. To demonstrate, particularly to a certification authority, that
sufficient testing has been performed, it is necessary to achieve the test coverage levels recommended or
mandated by safety standards and industry guidelines. Mutation testing provides an alternative or
complementary method of measuring test sufficiency, but has not been widely adopted in the safetycritical industry. The system provides an empirical evaluation of the application of mutation testing to
airborne software systems which have already satisfied the coverage requirements for certification.
The system mutation testing to safety-critical software developed using high-integrity subsets of
C and Ada, identify the most effective mutant types and analyze the root causes of failures in test cases.
Mutation testing could be effective where traditional structural coverage analysis and manual peer
review have failed. They also show that several testing issues have origins beyond the test activity and
this suggests improvements to the requirements definition and coding process. The system also
examines the relationship between program characteristics and mutation survival and considers how
program size can provide a means for targeting test areas most likely to have dormant faults. Industry
feedback is also provided, particularly on how mutation testing can be integrated into a typical
verification life cycle of airborne software. The system also covers the safety and criticality levels of
Java source code.
AN EFFECTIVE VERIFICATION AND VALIDATION STRATEGY FOR SAFETY-CRITICAL EMBEDDE...IJSEA
This paper presents the best practices to carry out the verification and validation (V&V) for a safetycritical
embedded system, part of a larger system-of-systems. The paper talks about the effectiveness of this
strategy from performance and time schedule requirement of a project. The best practices employed for the
V &Vis a modification of the conventional V&V approach. The proposed approach is iterative which
introduces new testing methodologies apart from the conventional testing methodologies, an effective way
of implementing the phases of the V&V and also analyzing the V&V results. The new testing methodologies
include the random and non-real time testing apart from the static and dynamic tests. The process phases
are logically carried out in parallel and credit of the results of the different phases are taken to ensure that
the embedded system that goes for the field testing is bug free. The paper also demonstrates the iterative
qualities of the process where the iterations successively find faults in the embedded system and executing
the process within a stipulated time frame, thus maintaining the required reliability of the system. This
approach is implemented in the most critical applications —-aerospace application where safety of the
system cannot be compromised
ICA provide vocational training courses under skill development initative on prescribed by DGET, GOVT.OF INDIA. This training is fully equipped to provide the candidates with the opportunity to develop through understandings of the taxation for individuals, companies, partnerships and other structures in India.
This is to compare the Returns of Fixed Deposits and Debt Oriented Hybrid Funds [Capital Protection Oriented Fund / Scheme (CPOF), Mutual Fund Monthly Income Plan / Scheme (MIP), Equity Savings Funds], to demonstrate how the latter is better.
computer system is a latest validation system in pharmaceutical industries.
To compliance with the good laboratory practice and good manufacturing practice.
it`s part of 211CFR part 11.
CHAPTER 15Security Quality Assurance TestingIn this chapter yoJinElias52
CHAPTER 15
Security Quality Assurance Testing
In this chapter you will
• Explore the aspects of testing software for security
• Learn about standards for software quality assurance
• Discover the basic approaches to functional testing
• Examine types of security testing
• Explore the use of the bug bar and defect tracking in an effort to improve the SDL process
Testing is a critical part of any development process and testing in a secure development lifecycle (SDL) environment is an essential part of the security process. Designing in security is one step, coding is another, and testing provides the assurance that what was desired and planned becomes reality. Validation and verification have been essential parts of quality efforts for decades, and software is no exception. This chapter looks at how and what to test to obtain an understanding of the security posture of software.
Standards for Software Quality Assurance
Quality is defined as fitness for use according to certain requirements. This can be different from security, yet there is tremendous overlap in the practical implementation and methodologies employed. In this regard, lessons can be learned from international quality assurance standards, for although they may be more expansive in goals than just security, they can make sense there as well.
ISO 9216
The International Standard ISO/IEC 9216 provides guidance for establishing quality in software products. With respect to testing, this standard focuses on a quality model built around functionality, reliability, and usability. Additional issues of efficiency, maintainability, and portability are included in the quality model of the standard. With respect to security and testing, it is important to remember the differences between quality and security. Quality is defined as fitness for use, or conformance to requirements. Security is less cleanly defined, but can be defined by requirements. One issue addressed by the standard is the human side of quality, where requirements can shift over time, or be less clear than needed for proper addressing by the development team. These are common issues in all projects, and the standard works to ensure a common understanding of the goals and objectives of the projects as described by requirements. This information is equally applicable to security concerns and requirements.
SSE-CMM
The Systems Security Engineering Capability Maturity Model (SSE-CMM) is also known as ISO/IEC 21827, and is an international standard for the secure engineering of systems. The SSE-CMM addresses security engineering activities that span the entire trusted product or secure system lifecycle, including concept definition, requirements analysis, design, development, integration, installation, operations, maintenance, and decommissioning. The SSE-CMM is designed to be employed as a tool to evaluate security engineering practices and assist in the definition of improvements to them. The SSE-CMM is organized into p ...
Extending the 20 critical security controls to gap assessments and security m...John M. Willis
Extending the 20 critical security controls to gap assessments and security maturity modeling.
Specifically, the controls are decomposed into Base Practices from a Process perspective.
Implementation approaches are viewed from a Robustness perspective.
This presentation reviews the regulatory requirements for intended use validation of SaaS-based EDC systems from the Sponsor and CRO perspective and provides best practices for implementing the proper validation in your organization.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
2. Verification & Validation
the process of checking that a product,
service, or system meets specifications and
that it fulfills its intended purpose. These are
critical components of a quality management
system such as ISO 9000. Sometimes
preceded with "Independent" (or IV&V) to
ensure the validation is performed by a
disinterested third party.
3. Verification
Quality control process that is used to
evaluate whether or not a product, service,
or system complies with regulations,
specifications, or conditions imposed at the
start of a development phase. Verification
can be in development, scale-up, or
production. This is often an internal process
4. Validation
Quality assurance process of
establishing evidence that provides a
high degree of assurance that a product,
service, or system accomplishes its
intended requirements. This often
involves acceptance of fitness for
purpose with end users and other
product stakeholders
5. Evaluation
a) analysis and checking of process(es) and procedure(s);
b) checking that process(es) and procedure(s) are being applied;
c) analysis of the correspondence between TOE design
representations;
d) analysis of the TOE design representation against the
requirements;
e) verification of proofs;
f) analysis of guidance documents;
g) analysis of functional tests developed and the results provided;
h) independent functional testing;
i) analysis for vulnerabilities (including flaw hypothesis);
j) penetration testing.
6.
7.
8. CC Paradigm System Acquisition Observations Regarding
Paradigm Commonality Among CC
and Acquisition
Paradigms
Protection Profile (PP) Request for Proposals Provides customer
desires, needs, and
requirements: "What is
wanted"
Security Target (ST) Proposals Indicates how the above
will be satisfied by
suppliers: "What will be
provided"
Target of Evaluation Delivered System Is the supplier's physical
(TOE) manifestation of above
Evaluated System Accepted System Shows that the three
preceding
representations are
sufficiently consistent
9.
10.
11. Significant of Vulneralability
a) eliminated -- that is, active steps should be taken to
expose, and remove or neutralize, all exercisable
vulnerabilities;
b) minimised -- that is, active steps should be taken to
reduce, to an acceptable residual level, the potential
impact of any exercise of a vulnerability;
c) monitored -- that is, active steps should be taken to
ensure that any attempt to exercise a residual
vulnerability will be detected so that steps can be taken
to limit the damage
12. Cause of Vulneralability
a) requirements -- that is, an IT product may possess
all the functions and features required of it and still
contain vulnerabilities that render it unsuitable or
ineffective with respect to security;
b) development -- that is, an IT product does not meet
its specifications and/or vulnerabilities have been
introduced as a result of poor development standards or
incorrect design choices;
c) operation -- that is, an IT product has been
constructed correctly to a correct specification but
vulnerabilities have been introduced as a result of
inadequate controls upon the operation
13. CC: Level Penjaminan Evaluasi
(EAL)
EAL1 : Fuctionality Tested
EAL2 : Structurally Tested
EAL3 : Methodically tested and checked
EAL4 : Methodically designed, tested, and
reviewed
EAL5 : Semi-formally designed and tested
EAL6 : Semi-formally verified, designed, and
tested
EAL7 : Formally verified, designed, and tested.
Diterapkan sesuai dengan keadaan atau kriteria
yang ditetapkan oleh kebutuhan pemakai.
15. Class in CC
Security Audit
Communication
Cryptographic
User Data Protection
Identification and Authentication
Security Management
Privacy
Protection of TSF
Resource Utilization
TOE Access
Trusted Path/Channel
16. Class in ASVS
Security Architecture
Authentication
Session Management
Access Control
Input Validation
Coding
Cryptography
Error Handling and Logging
Data Protection
Communication Security
HTTP Security
Security Configuration
Malicious Finding
Internal Security
17.
18. Information Security Testing and
Assesment Methodology (NIST,2008)
Planning
Information gathering about TOE, Ancaman, pengendalian akses
menangani ancaman, pendekatan evaluasi.
Pembuatan manajemen proyek untuk mencapai tujuan , lingkup,
kebutuhan, peran dan tanggung jawab tim, batasan, indikator
sukses, asumsi, sumber daya, timeline dan delivery.
Execution
Indentifikasi vulnerability dan melakukan validasi dengan benar.
Menjalankan metode dan teknik penilaian keamanan.
Hasil akhir berupa identifikasi vulnerability pada system komputer
dan proses organisasi.
Post-Execution
Analysis dan identifikasi vulnerability untuk menentukan akar
masalah, penetapan rekomendasi mitigasi, dan pembuatan
laporan akhir.
19. Teknik Penilaian
Review
Teknik pemeriksaan yang digunakan untuk
mengevaluasi sistem, aplikasi, jaringan, kebijakan,
prosedur untuk mencari vulnerability
Identifikasi dan Analysis Target
Identifikasi sistem, port, service, potensi vulnerability
Bisa dilakukan secara manual atau menggunakan
alat
Validasi Vunerability Target
Pembuktian Vulnerability yang ditemukan
Ex: password cracking, penetration testing, dan
social engineering
26. Trifecta
How do current Operation Work?
Penggunaan metrik untuk menentukan domain
masalah
How do they work differently from how
management think they works?
Akses ke kebijakan dan trust/resiko penilaian
dimap ke metrik masalah
How do they need to work?
Kalau ada gap antara metrik dan kebijakan atau
resiko penilaian
27.
28. Methodology (OSSTM)
1. Passively collect data of normal operations to comprehend the target.
2. Actively test operations by agitating operations beyond the normal
baseline.
3. Analyze data received directly from the operations tested.
4. Analyze indirect data from resources and operators (i.e. workers,
programs).
5. Correlate and reconcile intelligence from direct (step 3) and indirect
(step 4) data test results to determine operational security processes.
6. Determine and reconcile errors.
7. Derive metrics from both normal and agitated operations.
8. Correlate and reconcile intelligence between normal and agitated (steps
1 and 2) operations todetermine the optimal level of protection and
control which would best be implemented.
9. Map the optimal state of operations (step 8) to processes (step 5).
10. Create a gap analysis to determine what enhancements are needed for
processes governingnecessary protection and controls (step 5) to
achieve the optimal operational state (step 8) from the current one.
29. 6 langkah Analisis Keamanan
1. Build your knowledge of the target from a variety of the most
contemporary, factual resources while avoiding commercially biased
and speculative information.
2. Determine the global level of experience for the type of target and the
amount of information possibly known about it.
3. Determine any bias or ulterior motives in the information sources.
4. Translate jargon from information sources to similar or known words
for comparison because what may sound new or complicated may just
be a trick to differentiate something common.
5. Be sure the test equipment has been properly calibrated and the test
environment verified to assure the results are not contaminated by the
test itself.
6. Assure that the translation state of tools or test processes has been
removed as much as possible so that the results do not come from the
indirect sources in a process or the pre-analysis from some tools.
30. Keputusan Verifiksi
Unknown
Untested Target
Identified and Verified Limitation
False Positive and The means to generate
them
Failed Security Process and Procedure
Good Practices
Compliance
31. Network Sniffing
Merekam semua trafik jaringan untuk bahan analisis
Tools
TCPDUMP
WIRESHARK/TSHARK
Penempatan peralatan menjadi penting karena harus
betul-betul dapat menyadap komunikasi yang diinginkan
Harus dipasang setempat, tidak dapat secara remote
Contoh teknologi NetFlow dapat dilakukan secara
remote
32. Network Discovery
Test Target yang hidup
Simple test using ‘ping’, fail to detect firewall
because firewall reject ping request.
33. Port and Services Scanning
Try for all possible ports, 1 – 11000 for example
Test using standart communication to determine TCP or UDP
TCP test
Send SYN packet to target
Target replay by sending ACK packet
Send SYN ACK to target to start communication
Connection established.
UDP Test
If send UDP packet is not response assumed the port open
If send UDP packet is response assumed the port is closed or
open but not UDP services
Tools: Nmap and Hping