web.analysiscenter.veracode.com Open in urlscan Pro
2600:9000:214f:cc00:18:80fa:e640:93a1  Public Scan

Form analysis
1 forms found in the DOM

POST /login/

<form novalidate="novalidate" method="POST" action="/login/" data-se="o-form" slot="content" id="form19" class="primary-auth-form o-form o-form-edit-mode">
  <div data-se="o-form-content" class="o-form-content o-form-theme clearfix">
    <h2 data-se="o-form-head" class="okta-form-title o-form-head"> </h2>
    <div class="o-form-error-container" data-se="o-form-error-container"></div>
    <div class="o-form-fieldset-container" data-se="o-form-fieldset-container">
      <div data-se="o-form-fieldset" class="o-form-fieldset o-form-label-top margin-btm-5">
        <div data-se="o-form-label" class="okta-form-label o-form-label"><label for="okta-signin-username">Username / Email Address&nbsp;</label></div>
        <div data-se="o-form-input-container" class="o-form-input"><span data-se="o-form-input-username" class="o-form-input-name-username o-form-control okta-form-input-field input-fix focused-input"><input type="text" placeholder="" name="username"
              id="okta-signin-username" value="" aria-label="" autocomplete="username" aria-invalid="false" aria-required="true" required=""></span></div>
      </div>
      <div data-se="o-form-fieldset" class="o-form-fieldset o-form-label-top margin-btm-30">
        <div data-se="o-form-label" class="okta-form-label o-form-label"><label for="okta-signin-password">Password&nbsp;</label></div>
        <div data-se="o-form-input-container" class="o-form-input"><span data-se="o-form-input-password" class="o-form-input-name-password o-form-control okta-form-input-field input-fix"><input type="password" placeholder="" name="password"
              id="okta-signin-password" value="" aria-label="" autocomplete="current-password" aria-invalid="false" aria-required="true" required=""></span></div>
      </div>
    </div>
  </div>
  <div class="o-form-button-bar"><input class="button button-primary" type="submit" value="Log in" id="okta-signin-submit" data-type="save"></div>
</form>

Text Content

Username / Email Address 

Password 


Need help logging in?
 * Forgot Password
 * Change account region
 * Help

By clicking Log in, you are agreeing to our terms of service.

 1. 
 2. 
 3. 
    


PreviousNext
© 2006 - 2023 Veracode, Inc. 65 Network Drive, Burlington, MA 01803
+1-339-674-2500 support@veracode.com For use under U.S. Pat. Nos 9,672,355,
9,645,800, 9,405,906, 9,286,063, 9,207,920, 9,195,833, 8,365,155, 7,752,609, and
5,854,924, and patents pending.


VERACODE

End User Security and Confidentiality Responsibilities

To ensure the information security and confidentiality of your data, as an end
user of the Veracode Platform we require you agree to and comply with the
following user responsibilities and obligations.

Acceptable Use

Your use of the Veracode Platform and solutions is subject to the terms and
conditions agreed to in the agreement between Veracode and your organization
(either the Veracode End User Assessment Agreement located at
https://info.veracode.com/end-user-assessment-agreement.html or a separate
agreement executed by Veracode and your organization; in each case the
"Agreement"). You must not use the Veracode Platform or solutions for any
purpose other than those outlined in the Agreement.



You must use the Veracode Platform as designed and not make any attempts to gain
unauthorized access, elevate privileges, or extract data using mechanisms other
than those provided by the Platform for authorized users.



End User Credentials

You are responsible for all activities that occur on or through your user
account. Please adhere to the following guidelines with respect to your end user
credentials:





 * Your end user credentials are unique to you and for your sole use only. Do
   not share this information with anyone.
 * Do not write down your username and/or password
 * Be careful not to let your browser automatically save your username and
   password (of particular importance for users that do not have two-factor
   authentication)
 * Change your password periodically (at least every three months). Please note
   that you are required to change your password upon initial login.
 * Select a password that is not easily guessable (e.g. same as User ID) using
   the following recommended guidelines: 8 characters minimum, include
   upper/lower case characters, and at least one special character.
 * Any unauthorized use or suspected attempts to use your account must be
   reported to Veracode immediately using the notification procedure described
   below.
 * If applicable, lost or stolen RSA Tokens must be reported immediately to
   Veracode using the notification procedure described below.



Administrative Users

If you are granted administrator level privileges you will have the capability
to provision other user accounts and modify privileges of other accounts
associated with your organization. Veracode strongly recommends all
administrator level accounts to be two-factor. Customer administrators may not
set up other administrator level accounts - all requests for such should be sent
to Veracode Support. In addition, we recommend that you implement the following
procedures for account administration:





 * Formalize a request, review and approval process for members of your
   organization to request and gain accounts on the Platform. Document these
   requests and approvals to maintain an audit trail.
 * Terminate user accounts for terminated employees or employees that no longer
   need access due to change in role in a timely manner
 * Perform a periodic review of all Platform accounts for your organization and
   determine if they are still requiredOnly grant access to the lowest privilege
   level and least amount of information that is needed for a user to fulfill
   their job function



Reporting Obligations and Procedures

In order to provide the highest degree of information security and to protect
the confidentiality of your information, all matters of potential or material
impact must be reported immediately to Veracode. These include, but are not
limited to:





 * Unauthorized use of the Veracode Platform
 * Lost or compromised user credentials (including RSA Tokens)
 * Security and/or confidentiality breaches
 * Evidence of tampering with the online Platform
 * Potential security vulnerabilities for the online Platform
 * Issues or concerns regarding the Veracode Platform
 * If you are the primary contact for the Veracode Platform, you must send a
   written notification to Veracode Support in the event there is a change in
   employment status or role of one of the authorized users for your company
   (including yourself) such that they no longer require or are authorized to
   have access to the Veracode Platform. Your request should specify the date on
   which you would like Veracode to disable the Platform account. Please allow 1
   business day to process requests and plan accordingly.



Personal Information Submitted to the Veracode Platform

Veracode's Platform is located and operates in the United States. If you are
located outside of the United States, please be aware that information you
submit to the Veracode Platform, including personal information such as your
name, email address and similar business related contact information, is being
transferred to and will be processed in the United States. By accepting these
Usage Guidelines or by submitting such information to the Veracode Platform, you
fully understand and unambiguously consent to this transfer, processing and
storage of your information in the United States, a jurisdiction in which the
privacy laws may not be as comprehensive as those in the country where you
reside and/or are a citizen.

Contact

You may contact Veracode using any of the following methods to report security
and confidentiality related issues:





 * Email: support@veracode.com
 * Phone: 1-877-837-2203
 * Technical Account Manager or Customer Success Manager (if applicable)