This 30-minute introductory consultation is used to discuss your organization’s security assessment needs and determine whether ELX Security Consulting is the right fit for the engagement.

The purpose of the call is to understand your objectives, target environment, business or mission drivers, timeline, authorization boundaries, and reporting expectations. This is a scoping and discovery conversation only. No testing activity begins until proper authorization, scope, and agreement are in place.

ELX supports offensive security and software assurance engagements, including penetration testing, web and API application security testing, reverse engineering, exploitability validation, fuzz testing support, static and dynamic analysis, and secure code review.

During the call, we may discuss:

• The type of assessment needed, such as black-box, gray-box, or white-box penetration testing
• The target domain, such as web applications, APIs, internal or external networks, wireless environments, mobile applications, thick clients, binaries, or source code
• Whether the engagement is primarily focused on penetration testing, software assurance, exploitability validation, or remediation verification
• Known concerns, previous findings, suspected weaknesses, compliance drivers, or security objectives
• Testing constraints, sensitive systems, production-impact concerns, blackout windows, and rules of engagement
• Expected deliverables, including executive summaries, technical findings, evidence, remediation guidance, and retest criteria
• Timeline, access requirements, communication expectations, and next steps

To prepare for the call, please be ready to discuss:

• The organization or business unit requesting the assessment
• The general type of asset or environment to be assessed
• Whether the target is internal, external, cloud-hosted, web-based, API-based, mobile, thick-client, source-code, binary, or mixed
• The assessment style needed, if known: black-box, gray-box, or white-box
• Your desired timeline or deadline
• Any known security concerns, previous assessment results, or remediation goals
• Whether you have authority to request testing for the target environment
• Any reporting, compliance, or stakeholder requirements

The objective of the call is to determine scope, feasibility, engagement fit, and the appropriate next step. After the consultation, ELX may recommend a formal scoping discussion, request additional technical details, or provide a proposal for the requested assessment.

This meeting does not authorize security testing, scanning, exploitation, access attempts, or vulnerability validation against any system. All security testing requires a signed agreement, defined scope, and written authorization.