leap.hcltechsw.com Open in urlscan Pro
52.3.3.79  Public Scan

Submitted URL: https://content.comms.hcltechsw.com/deliverirs/servlet/IRSL?v=5&a=214&r=214714&m=5306&l=5&e=2&x=2460232.0
Effective URL: https://leap.hcltechsw.com/apps/anon/org/app/f86428a6-bd9c-4326-89df-d0d8ed1cfcf2/launch/index.html?form=F_Form1?utm_source...
Submission: On October 13 via api from US — Scanned from DE

Form analysis 2 forms found in the DOM

POST javascript:;

<form action="javascript:;" method="post" class="lotusDialog lotusForm lfDialog" dojoattachpoint="form" autocomplete="off">
  <div class="lotusDialogHeader lfDialogTitle" dojoattachpoint="lotusDialogHeader">
    <h1 dojoattachpoint="titleBar" class="lotusHeading" style="cursor: default;">
      <span id="freedom_widget_solution_environment_CurrentItemViewDialog_0_dialog_title" dojoattachpoint="titleNode">Application View</span>
    </h1>
    <a role="button" class="lotusDialogClose" href="javascript:;" dojoattachevent="onclick: onCancelAction" dojoattachpoint="closeButtonNode" title="Close"><img alt="Close" src="../../../../../open/9.2.1.14/dojo/resources/blank.gif"><span class="lotusAltText a11y-text" style="cursor: pointer; display:none">X</span></a>
  </div>
  <div dojoattachpoint="containerNode" class="lfDialogContainer" role="dialog" aria-labelledby="freedom_widget_solution_environment_CurrentItemViewDialog_0_dialog_title">
    <div class="lotusDialogContent lfDialogContent lfAppFormArea" dojoattachpoint="contentNode">
    </div>
  </div>
  <!-- Button is never show but needs to be present for RPT validation -->
  <button type="submit" style="display:none;">_</button>
</form>

POST javascript:;

<form action="javascript:;" method="post" class="lotusDialog lotusForm lfDialog" dojoattachpoint="form" autocomplete="off">
  <div class="lotusDialogHeader lfDialogTitle" dojoattachpoint="lotusDialogHeader">
    <h1 dojoattachpoint="titleBar" class="lotusHeading" style="cursor: default;">
      <span id="freedom_widget_common_environment_ConfirmationWithDetailsDialog_0_dialog_title" dojoattachpoint="titleNode"></span>
    </h1>
    <a role="button" class="lotusDialogClose" href="javascript:;" dojoattachevent="onclick: onCancelAction" dojoattachpoint="closeButtonNode" title="Close" style="display: none;"><img alt="Close" src="../../../../../open/9.2.1.14/dojo/resources/blank.gif"><span class="lotusAltText a11y-text" style="cursor: pointer; display:none">X</span></a>
  </div>
  <div dojoattachpoint="containerNode" class="lfDialogContainer" role="dialog" aria-labelledby="freedom_widget_common_environment_ConfirmationWithDetailsDialog_0_dialog_title">
    <!-- (c) Copyright HCL Technologies Ltd. 2018. All rights reserved.  -->
    <div>
      <div class="lotusDialogContent lfDialogContent">
        <div dojoattachpoint="message"></div>
        <table cellpadding="0" cellspacing="0" style="padding-top: 0.5em; padding-bottom: 0.5em" dojoattachpoint="detailsHeader" role="presentation">
          <tbody>
            <tr>
              <td style="width: 12px; height: 16px; vertical-align:middle" dojoattachpoint="imageContainerNode">
                <span class="expandIcon" dojoattachevent="onclick:expandCollapse" dojoattachpoint="expandCollapseButton" alt=""></span>
              </td>
              <td dojoattachpoint="titleContainer" style="vertical-align:middle">
                <a href="javascript: void(0)" dojoattachevent="onclick:expandCollapse" dojoattachpoint="detailsLink">More Details...</a>
              </td>
            </tr>
          </tbody>
        </table>
        <div class="confirmDetail" style="display:none; font-style: italic;" dojoattachpoint="detailsView"></div>
        <div dojoattachpoint="question" style="padding-top: 1em; outline:0px;" tabindex="1"></div>
      </div>
      <div class="lotusDialogFooter lfDialogFooter" footernoscrollbar="true">
        <span dojoattachpoint="yesButtonContainer">
          <span class="dijit dijitReset dijitInline dijitButton lfFormBtn lotusFormButton yes-btn" data-dojo-attach-event="onclick:__lfFormBtnOnClick" role="presentation" widgetid="dijit_form_Button_4"><span
              class="dijitReset dijitInline dijitButtonNode" data-dojo-attach-event="ondijitclick:__onClick" role="presentation"><span class="dijitReset dijitStretch dijitButtonContents" data-dojo-attach-point="titleNode,focusNode" role="button"
                aria-labelledby="dijit_form_Button_4_label" id="dijit_form_Button_4" title="Yes" tabindex="2" style="user-select: none;"><span class="dijitReset dijitInline dijitIcon dijitNoIcon" data-dojo-attach-point="iconNode"></span><span
                  class="dijitReset dijitToggleButtonIconChar">●</span><span class="dijitReset dijitInline dijitButtonText" id="dijit_form_Button_4_label" data-dojo-attach-point="containerNode">Yes</span></span></span><input type="button" value=""
              class="dijitOffScreen" data-dojo-attach-event="onclick:_onClick" tabindex="-1" role="presentation" aria-hidden="true" data-dojo-attach-point="valueNode"></span>
        </span>
        <span dojoattachpoint="noButtonContainer">
          <span class="dijit dijitReset dijitInline dijitButton lfFormBtn lotusFormButton no-btn" data-dojo-attach-event="onclick:__lfFormBtnOnClick" role="presentation" widgetid="dijit_form_Button_5"><span
              class="dijitReset dijitInline dijitButtonNode" data-dojo-attach-event="ondijitclick:__onClick" role="presentation"><span class="dijitReset dijitStretch dijitButtonContents" data-dojo-attach-point="titleNode,focusNode" role="button"
                aria-labelledby="dijit_form_Button_5_label" id="dijit_form_Button_5" title="No" tabindex="3" style="user-select: none;"><span class="dijitReset dijitInline dijitIcon dijitNoIcon" data-dojo-attach-point="iconNode"></span><span
                  class="dijitReset dijitToggleButtonIconChar">●</span><span class="dijitReset dijitInline dijitButtonText" id="dijit_form_Button_5_label" data-dojo-attach-point="containerNode">No</span></span></span><input type="button" value=""
              class="dijitOffScreen" data-dojo-attach-event="onclick:_onClick" tabindex="-1" role="presentation" aria-hidden="true" data-dojo-attach-point="valueNode"></span>
        </span>
      </div>
    </div>
  </div>
  <!-- Button is never show but needs to be present for RPT validation -->
  <button type="submit" style="display:none;">_</button>
</form>

Text Content

Top


TURN ON JAVASCRIPT

JavaScript has been disabled in your web browser. HCL Leap requires JavaScript
in order to function. Once you have turned it on, please refresh the page.

Refresh the page to continue.


HCL Leap
 * Welcome Guest
 * Log Out
 * Help


 * 2022 SECURITY TESTING TRENDS SURVEY

 * 

Loading...


WHICH FORM DO YOU WANT TO RUN?

Please select one of the following forms:

 * Form 1

Information Application will be viewed in a dialog.
Error
< >

< >



Information Form was removed
Form 1 - Start *

 1. ●Print
 2. ●Delete Record
 3. ●Close

 


2022 APPLICATION SECURITY TESTING TRENDS SURVEY 

 

Thank you for participating in this short survey. Your input is invaluable to
helping us better understand recent trends in Application Security Testing as
they pertain to your industry. As a thank you for your answers, we will share
the entire report with you when it’s published later this year. 
 

This survey should take less than 5 minutes to complete. Answers to all
questions are required.  

 



+ - Section



+ - Section


* 1. Who is responsible for Application Security Testing in your organization?
Please select all that apply.
 * Developers
 * DevOps
 * Security Experts
 * External Teams

This value is required



* 2. Which is the biggest challenge you see with your AppSec program?
 * Knowing which applications to focus on
 * Lack of resources to handle security testing
 * Prioritizing findings for remediation
 * Fixing vulnerabilities
 * Scanning the application with good levels of coverage
 * Keeping up with new technologies (Blockchain, K8s, etc.)
 * Don’t know or don’t have an AppSec program





* 3. At what phase in the Software Development Lifecycle (SDLC) does your
organization begin testing applications for security vulnerabilities?
 * During Development
 * During Build
 * Prior to Release
 * After Release
 * Throughout the life cycle
 * Only when there is an issue
 * Never





* 4. How satisfied are you with the time it takes to remediate security
vulnerabilities?
Select one
-



+

Extremely Satisfied
Mostly Satisfied
Satisfied
Not Very Satisfied
Not Satisfied at all





* 5. What challenges have you faced when adopting application security
technology? Please select all that apply.
 * Concerns over slowing down the Software Development Lifecycle (SDLC)
 * Concerns over cost
 * Lack of security expertise within the organization
 * Can’t get all stakeholders in agreement on need
 * My organization places too much trust in third party applications
 * None

This value is required



* 6. How do you perform application security vulnerability risk management?
Please select all that apply.
 * Based on reported criticality by the application security tool
 * Use CVSS score
 * Custom risk metric
 * Using centralized vulnerability management tools
 * Third party review

This value is required



* 7. Which of these technologies are you currently using? Please select all that
apply.
 * DAST – Testing running web applications and APIs
 * SAST – Test the code/bytecode/binaries
 * IAST – Monitor application for vulnerabilities from the inside
 * SCA – Check for vulnerable 3rd party components
 * None of the Above

This value is required



* 8. Which of these technologies would you like to be using that you are not
currently? Please select all that apply.
 * DAST – Testing running web applications and APIs
 * SAST – Test the code/bytecode/binaries
 * IAST – Monitor application for vulnerabilities from the inside
 * SCA – Check for vulnerable 3rd party components

This value is required



* 9. If you use a DAST engine, how often do you run DAST scans for an
application?
 * Daily
 * Weekly
 * Monthly
 * Quarterly
 * 1-2 times a year
 * Never - I do not use DAST for security testing





* 10. If you use a SAST engine, how early do you perform SAST?
 * Right when coding - Development IDE is integrated with SAST
 * On every code check-in
 * On every build
 * Once a release
 * Never - I do not use SAST for testing





* 11. Are your security scans integrated as part of the CI/CD pipeline?
Select one
-



+

Already Integreated
Plan to Integrate within 6 months
Plan to Integrate post 6 months
Not in the plans





* 12. Do your developers have access to secure coding guidelines?
 * Yes
 * No
 * Don't Know





* 13. What industry does your organization operate in?
 * Finance/Banking
 * Agriculture
 * Consumer goods
 * Manufacturing
 * Healthcare
 * Pharma
 * Oil and gas
 * IT
 * Retail
 * Telecommunications
 * Transportation
 * Utility





* 14. In what geographic region do you reside?
 * Africa
 * Asia
 * Caribbean
 * Central America
 * Europe
 * North America
 * Oceania
 * South America





* 15. What is your current role?
 * Developer
 * Product Manager
 * Security Manager
 * Pen Tester
 * CISO
 * None of the above








+ - Section


* Email
&



+ - Section


* First Name
&

* Last Name
&






* Company
&


* Job Title
&











+ - Section


* I am not a U.S. Federal Government employee or agency, nor am I submitting on
behalf of one.

HCL provides software and services to the U.S. Federal Government through its
partner ImmixGroup, Inc. https://hcltechsw.com/resources/us-government-contact

* I acknowledge to have read and understood all the contents of HCL's privacy
policy.

You can withdraw your marketing consent at any time by submitting an opt-out
request. Also you may unsubscribe from receiving marketing emails by clicking
the unsubscribe link in each email.


HCL Privacy Policy | Update your communication preferences









The Application Configuration section must be completed for every new
application. Every field in the Application Configuration section will need to
be adjusted.

 

The remaining sections are optional but they should be reviewed.



+ - Application Configuration


* CampaignCode
&

* Required - It is the Unica Campaign Code. E.g. C000000159



* OfferCode
&

* Required - It is the Unica Offer Code. E.g. 000000075

* Product Key for Lead Lookup
&

This is a part of the lookup key used to retrieve the regions as well as
retrieve the sales lead information. Allowable values are: AppScan, BigFix,
Commerce, Domino, DX, OneTest, Unica, Volt MX, Workload Automation, Z. - Domino
is used for most DS products (except DX)

* CRM_WebFormProductName
&

* Required - Proper name to match CRM - Usually includes "HCL" e.g. HCL Domino

* CRM_WebFormProducts
&

* Optional and usually blank

* CRM_Topic
&

* Required - This is the topic in CRM. Format is Webform_productName Form
Description - E.g. Webform_BigFix Download ESG Report

* PageURL
&

This is the URL the end user used to get to the Leap Form. For standalone pages
it is the Leap URL for embedded it is the website host page URL.

* LeapFormName
&

This should be the same as the application name / browser tab title.

* Description
This field is usually blank here as it is concantenated with other data before
it is sent to Unica/CRM. The UTM fields and Page URL will automatically be added
so do not put them in here. If your form includes custom fields that should go
to Unica/CRM then add them to the AfterSave event.


* EmailTo
&

Leave blank and emails will not be sent.

* EmailCC
&

Usually blank

* EmailSubject
&

The Company name will be added automatically to the end of the string

* EmailLeadInParagraph
The default content contains most of the user data. Anything here would be in
addition to the default content.







+ - Application Fields For This Application



Add any additional hidden custom fields to this section


* EMail Link
&

Used programmatically if a link needs to be programmatically generated for use
in the outgoing email or completion screen








+ - Not Used In This Form



+ - Section


* Country:
Germany

* State/Province







These fields were in the original base template but are not used in most
applications. Rather than delete them and possibly need to update the javascript
or integration the unused fields should be moved to here.


* What is your relationship with HCL?
 * Customer
 * Prospective Customer
 * Business Partner
 * Employee
 * Other



* Phone number
&


* If other, please explain:
&


* In order for us to better serve you, please let us know what you are most
interested in:
 * Reinstating your software
 * Scheduling a demo
 * Technical support or licensing
 * General Inquiry



* Inquiry:







+ - Generic Application Fields



Everything in this section is used by the application code. The fields are all
normally blank.


* Email Domain
&


* Blocked Domain
&


* MS Auth


* Referrer
&


* AssignedLeadUID
&


* AssignedLead
&


* IP Address
&


* IP Country
&


* IP State
&


* IP City
&


* F_LeadLookupKey
&


* F_RegionLookupKey
&


* F_ShowStateProvince
&


* LeapFormId
&

This is the UUID of this app.






+ - Unica Fields


* MailingId
&


* InviteCode
&


* Source
&


* Time
&


* Lead Owner GUID
&


* Lead Owner GUName
&


* Lead Owner GUEMail
&


* utm_source
&


* utm_medium
&


* utm_campaign
&







+ - Tracking Fields


Do not include any tracking

This for is embedded so perform only conversion tracking on press of Submit
button


+ - Tracking Default Values (usually do not touch)


* Google gtag id
&

AW-710009114;UA-111445871-12 are our standard values - Multivalues are allowed -
separated by a semicolon

* Twitter pixel id
&

02egc is our standard value

* LinkedIn partner id
&

1487452 is our standard value






+ - Tracking Conversion Code (always custom or blank)


* Google gtag conversion code
&

This value is unique to every application - e.g.
AW-710009114/cr76CJOwntsBEJrCx9IC

* Twitter Conversion trackPid
&

This value is unique to every application (e.g. o3emb)

* Linkedin Conversion id
&

This value is unique to every application (e.g. 2915185)

* Facebook Pixel id / Conversion code
&

This value is unique to every application (e.g 365306711042623)





















There are no pages to display. Contact the person who sent you the link to this
application.

 1. ●Submit



●OK


APPLICATION VIEW

X

_




X

More Details...



●Yes ●No
_