Resources
Application Dependency Mapping: The Complete Guide (faddom.com)
Open source Application review
This is the process to review all applications
Evaluating open-source software (OSS) involves several steps to ensure it
aligns with your needs and quality standards. Let’s dive into a detailed
procedure for reviewing OSS:
1. Functionality and Purpose Assessment:
o Understand the purpose of the software. Does it solve your specific problem
or meet your requirements?
o Evaluate its features, compatibility, and ease of use.
o Consider whether it integrates well with your existing tools.
2. Community and Support Evaluation:
o Check the size and activity of the developer community. Active projects tend
to have better support and updates.
o Look for documentation, forums, and mailing lists for community support.
o Investigate the responsiveness of maintainers to issues and pull requests.
3. Code Quality and Security Inspection:
o Examine the source code for readability, maintainability, and adherence to
coding standards.
o Assess security practices. Look for regular security audits, vulnerability
management, and timely patches.
o Use static analysis tools to identify potential issues.
4. Licensing and Legal Considerations:
o Understand the software’s license (e.g., GPL, MIT, Apache). Ensure it aligns
with your project’s goals.
o Be aware of any copyleft provisions that might affect your project.
o Check for any legal risks related to third-party dependencies.
5. Popularity and Reputation Research:
o Check the project’s popularity, stars, forks, and downloads on platforms like
GitHub.
o Read reviews, blog posts, and case studies to gauge its reputation.
o Investigate any historical security incidents or controversies.
6. Dependencies and Compatibility Verification:
o Inspect its dependencies. Are they well-maintained and secure?
o Verify compatibility with your existing tools, libraries, and frameworks.
o Consider how often the project releases updates.
7. Performance and Scalability Testing:
o Test the software’s performance under different conditions.
o Consider scalability if your project may grow in the future.
o Evaluate resource usage and responsiveness.
Fully evaluate the executable size
1. Check it with Windows itself
2. Upload the file to VirusTotal
3. Who is the publisher?
4. Run it in Windows Sandbox
5. Check the .exe’s network activity for suspicious behavior
https://www.glasswire.com/processes/#scan-file-with-windows-security
1. Review manufacture
2. Upload to https://www.virustotal.com/gui/home/upload
3. Wireshark: This powerful tool allows you to capture and analyze network packets.
However, it doesn’t directly filter by process ID. You’ll need to identify the ports the
program uses and filter accordingly 1.
4. Microsoft Network Monitor: Although it’s no longer actively developed, it
can trace specific process connections. Make sure to run it as an
administrator to see all data1.
5. Resource Monitor: Access it via Task Manager (File > New Task
> resmon). It provides a quick overview of how many bytes a program is
sending
6. Check out Process Monitor at -
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
a. Microsoft Process Monitor - Using Process Monitor to trace execution of a
program - Microsoft Community
b. Troubleshooting with Process Monitor - Microsoft Community Hub
c. Check out process
explorer: http://technet.microsoft.com/de-de/sysinternals/bb896653
.aspx
Identify Applications, Dependences, resources and
permission.
1. Application dependency mapping is the process of visually laying out the
relationships between applications and their dependencies within an IT
environment. It provides an accurate map of your entire IT ecosystem,
including infrastructure, services, and applications, along with their
interconnections1. Here are some key points:
2. What is Application Dependency Mapping (ADM)?
o ADM identifies and documents the relationships between components of an
application and their dependencies on other systems, infrastructure, and
services2.
o It helps organizations understand how different components relate to each
other and how changes in one application might impact others 3.
3. Methods for Application Dependency Mapping:
o Sweep and Poll: This lightweight method sweeps and pings IP addresses,
gathering information about devices and applications. It’s easy to perform
but may be less accurate in dynamic environments 1.
o Network Monitoring: Analyzing network traffic patterns in real time allows
detection of dependency changes. It’s effective even in less understood
systems1.
4. Benefits of Dependency Mapping:
o Enhanced visibility: Understand your IT landscape, identify gaps,
redundancies, and optimization opportunities.
o Better risk management: Recognize dependencies to prevent issues caused
by changes within the infrastructure1.
Accurate application dependency mapping is crucial for maintaining a
healthy and efficient IT environment.
