asvs checklist

ASVS_Results

Security Category	Valid criteria	Total criteria	Validity Percentage	ASVS Level Acquired
Architecture	26	32	81.25
Authentication	0	57	0.00
Session Management	15	19	78.95
Access Control	7	9	77.78
Input Validation	24	28	85.71
Cryptography at Rest	7	12	58.33
Error Handling and Logging	10	11	90.91
Data Protection	0	17	0.00
Communication Security	6	8	75.00
Malicious Code	7	9	77.78
Business Logic	6	7	85.71
Files and Resources	14	15	93.33
Web Service	0	15	0.00
Configuration	14	21	66.67
Total	136	260	52.31

&A

Page &P

Validity Percentage

Validity Percentage Architecture Authentication Session Management Access Control Input Validation Cryptography at Rest Error Handling and Logging Data Protection Communication Security Malicious Code Business Logic Files and Resources Web Service Configuration 81.25 0 78.94736842105263 77.777777777777786 85.714285714285708 58.333333333333336 90.909090909090907 0 75 77.777777777777786 85.714285714285708 93.333333333333329 0 66.666666666666657

Architecture

Area	#	ASVS Level	CWE	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Secure Software Development Lifecycle Requirements	1.1.1	2		Verify the use of a secure software development lifecycle that addresses security in all stages of development. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	EVERY STAGE	NONE	YES	YES
	1.1.2	2	1053	Verify the use of threat modeling for every design change or sprint planning to identify threats, plan for countermeasures, facilitate appropriate risk responses, and guide security testing.	Non-valid	DESIGN STAGE	NONE	NO	NO	There was no threat modeling conducted
	1.1.3	2	1110	Verify that all user stories and features contain functional security constraints, such as "As a user, I should be able to view and edit my profile. I should not be able to view or edit anyone else's profile"	Valid	DEVELOPMENT STAGE	NONE	YES	YES	Proper Authentication, and Session Mangment in addtion to Built-in controls to allow access to resources based on role (RBAC) have been implemented to fullfill this requirement
	1.1.4	2	1059	Verify documentation and justification of all the application's trust boundaries, components, and significant data flows.	Valid	DESIGN STAGE	NONE	YES	YES	Documentation created for all the Labs conducted
	1.1.5	2	1059	Verify definition and security analysis of the application's high-level architecture and all connected remote services. ([C1](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DESIGN STAGE	NONE	YES	YES	Documentation created for all the Labs conducted
	1.1.6	2	637	Verify implementation of centralized, simple (economy of design), vetted, secure, and reusable security controls to avoid duplicate, missing, ineffective, or insecure controls. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	1.1.7	2	637	Verify availability of a secure coding checklist, security requirements, guideline, or policy to all developers and testers.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Authentication Architectural Requirements	1.2.1	2	250	Verify the use of unique or special low-privilege operating system accounts for all application components, services, and servers. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT STAGE	NONE	YES	YES	Yes, separate accounts and permissions where created to have limited access to only the resources the application or software needs (Least Privilege)
	1.2.2	2	306	Verify that communications between application components, including APIs, middleware and data layers, are authenticated. Components should have the least necessary privileges needed. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT STAGE	NONE	YES	YES	Baseline images validated on Cybera Infrastructure
	1.2.3	2	306	Verify that the application uses a single vetted authentication mechanism that is known to be secure, can be extended to include strong authentication, and has sufficient logging and monitoring to detect account abuse or breaches.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	TLS Certificate with strong ciphers used, in addition to the usage of Plugins (Jetpack) for logging on WordPress
	1.2.4	2	306	Verify that all authentication pathways and identity management APIs implement consistent authentication security control strength, such that there are no weaker alternatives per the risk of the application.	Valid	DEVELOPMENT AND TEST STAGES	QUALYS	YES	YES	TLS Certificate with strong ciphers used, in addition to the usage of Plugins for logging on WordPress
Access Control Architectural Requirements	1.4.1	2	602	Verify that trusted enforcement points such as at access control gateways, servers, and serverless functions enforce access controls. Never enforce access controls on the client.	Valid	DEVELOPMENT AND TEST STAGES	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	YES	YES	Using UFW to limit connections to only HTTPS and SSH and Linux permissions and separate accounts created for certain access to software and files(ex database only account)
	1.4.2	2	284	Verify that the chosen access control solution is flexible enough to meet the application's needs.	Valid	EVERY STAGE	NONE	YES	YES	Built-in controls to allow access to resources based on role (RBAC) is implemented and includes roles such as: Administrator Editor Author Contributor Subscriber
	1.4.3	2	272	Verify enforcement of the principle of least privilege in functions, data files, URLs, controllers, services, and other resources. This implies protection against spoofing and elevation of privilege.	Valid	EVERY STAGE	NONE	YES	YES	WP-All-In-One-Security and Jetpack Plugin has basic protections in place to help mitgate these concerns
	1.4.4	2	284	Verify the application uses a single and well-vetted access control mechanism for accessing protected data and resources. All requests must pass through this single mechanism to avoid copy and paste or insecure alternative paths. ([C7](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	EVERY STAGE	NONE	YES	YES	WP-All-In-One-Security Plugin has basic protections in place to help mitgate this in certain elements in the particular case manual vetting of account creation among other areas
	1.4.5	2	275	Verify that attribute or feature-based access control is used whereby the code checks the user's authorization for a feature/data item rather than just their role. Permissions should still be allocated using roles. ([C7](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	EVERY STAGE	NONE	YES	YES	WP-All-In-One-Security Plugin has basic protections in place to help mitgate this in certain elements. In addition, WP application handles accounts according to internal functioning
Input and Output Architectural Requirements	1.5.1	2	1029	Verify that input and output requirements clearly define how to handle and process data based on type, content, and applicable laws, regulations, and other policy compliance.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	1.5.2	2	502	Verify that serialization is not used when communicating with untrusted clients. If this is not possible, ensure that adequate integrity controls (and possibly encryption if sensitive data is sent) are enforced to prevent deserialization attacks including object injection.	Valid	EVERY STAGE	NONE	YES	YES	Yes, all tools and software used are from trusted sources and repositiories used and vetted by organizations
	1.5.3	2	602	Verify that input validation is enforced on a trusted service layer. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	EVERY STAGE	NONE	YES	YES	Inputs are validated automatically in addition to manual vetting of posts by admin
	1.5.4	2	116	Verify that output encoding occurs close to or by the interpreter for which it is intended. ([C4](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))	Valid	EVERY STAGE	NONE	YES	YES	PHP handles the serialization of WordPress via API calls
Cryptographic Architectural Requirements	1.6.1	2	320	Verify that there is an explicit policy for management of cryptographic keys and that a cryptographic key lifecycle follows a key management standard such as NIST SP 800-57.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	1.6.2	2	320	Verify that consumers of cryptographic services protect key material and other secrets by using key vaults or API based alternatives.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	1.6.3	2	320	Verify that all keys and passwords are replaceable and are part of a well-defined process to re-encrypt sensitive data.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	1.6.4	2	320	Verify that the architecture treats client-side secrets--such as symmetric keys, passwords, or API tokens--as insecure and never uses them to protect or access sensitive data.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Error, Logging and Auditing Architectural Requirements	1.7.1	2	1009	Verify that a common logging format and approach is used across the system. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DESIGN STAGE	NONE	YES	YES	TLS Certificate with strong ciphers used, in addition to the usage of Plugins (Jetpack) for logging on WordPress
	1.7.2	2		Verify that logs are securely transmitted to a preferably remote system for analysis, detection, alerting, and escalation. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	TLS Certificate with strong ciphers used, in addition to the usage of Plugins for logging on WordPress
Data Protection and Privacy Architectural Requirements	1.8.1	2		Verify that all sensitive data is identified and classified into protection levels.	Non-valid	DESIGN STAGE	NONE	NO	NO	This was not done in the current scope
	1.8.2	2		Verify that all protection levels have an associated set of protection requirements, such as encryption requirements, integrity requirements, retention, privacy and other confidentiality requirements, and that these are applied in the architecture.	Non-valid	DESIGN STAGE	NONE	NO	NO	This was not done in the current scope
Communications Architectural Requirements	1.9.1	2	319	Verify the application encrypts communications between components, particularly when these components are in different containers, systems, sites, or cloud providers. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NESSUS, KALI LINUX/METASPLOIT, QUALYS	YES	YES	Creation of TLS Certificate with strong ciphers used and verified through multiple tools
	1.9.2	2	295	Verify that application components verify the authenticity of each side in a communication link to prevent person-in-the-middle attacks. For example, application components should validate TLS certificates and chains.	Valid	DEVELOPMENT AND TEST STAGES	NESSUS, KALI LINUX/METASPLOIT, QUALYS	YES	YES	Creation of TLS Certificate with strong ciphers used and verified through multiple tools
Malicious Software Architectural Requirements	1.10.1	2	284	Verify that a source code control system is in use, with procedures to ensure that check-ins are accompanied by issues or change tickets. The source code control system should have access control and identifiable users to allow traceability of any changes.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Business Logic Architectural Requirements	1.11.1	2	1059	Verify the definition and documentation of all application components in terms of the business or security functions they provide.	Valid	EVERY STAGE	NONE	YES	YES	Documentation created for all the Labs conducted
	1.11.2	2	362	Verify that all high-value business logic flows, including authentication, session management and access control, do not share unsynchronized state.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	1.11.3	2	367	Verify that all high-value business logic flows, including authentication, session management and access control are thread safe and resistant to time-of-check and time-of-use race conditions.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Secure File Upload Architectural Requirements	1.12.1	2	552	Verify that user-uploaded files are stored outside of the web root.	Valid	DEVELOPMENT AND TEST STAGES		YES	YES	Only superficial file inspection via file extension examination is done
	1.12.2	2	646	Verify that user-uploaded files - if required to be displayed or downloaded from the application - are served by either octet stream downloads, or from an unrelated domain, such as a cloud file storage bucket. Implement a suitable Content Security Policy (CSP) to reduce the risk from XSS vectors or other attacks from the uploaded file.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Storage of documents contained within the www web folder, which has restricted access to only read and secured write permissions through certain accounts only. In addition to Jetpack Plugin providing images, CSS and other forms from its own servers.
Configuration Architectural Requirements	1.14.1	2	923	Verify the segregation of components of differing trust levels through well-defined security controls, firewall rules, API gateways, reverse proxies, cloud-based security groups, or similar mechanisms.	Valid	DEVELOPMENT STAGE	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	YES	YES	Through the use of UFW to limit connections to only HTTPS and SSH and Linux permissions and separate accounts created for certain access to software and files(ex database only account)
	1.14.2	2	494	Verify that binary signatures, trusted connections, and verified endpoints are used to deploy binaries to remote devices.	Valid	EVERY STAGE	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	YES	YES	Yes, all tools and software used are from trusted sources and repositiories used by many users
	1.14.3	2	1104	Verify that the build pipeline warns of out-of-date or insecure components and takes appropriate actions.	Valid	DEVELOPMENT AND TEST STAGES	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	YES	YES	This can be seen and configured on the Wordpress admin Webpage and can be upgraded with a single click
	1.14.4	2		Verify that the build pipeline contains a build step to automatically build and verify the secure deployment of the application, particularly if the application infrastructure is software defined, such as cloud environment build scripts.	Non-valid	TESTING STAGE	DOES NOT APPLY	NO	NO	There is no automation configured
	1.14.5	2	265	Verify that application deployments adequately sandbox, containerize and/or isolate at the network level to delay and deter attackers from attacking other applications, especially when they are performing sensitive or dangerous actions such as deserialization. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	TESTING STAGE	DOES NOT APPLY	NO	NO	There is no containers or docker images setup
	1.14.6	2	477	Verify the application does not use unsupported, insecure, or deprecated client-side technologies such as NSAPI plugins, Flash, Shockwave, ActiveX, Silverlight, NACL, or client-side Java applets.	Non-valid	TESTING STAGE	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	NO	NO	Javascript is a requirement to be used in the development of the application

&A

Page &P

Authentication

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	Source Code Reference	Comment	Tool Used
Password Security Credentials	2.1.1	1	521	5.1.1.2	Verify that user set passwords are at least 12 characters in length (after multiple spaces are combined). ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.1.2	1	521	5.1.1.2	Verify that passwords 64 characters or longer are permitted but may be no longer than 128 characters. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.1.3	1	521	5.1.1.2	Verify that password truncation is not performed. However, consecutive multiple spaces may be replaced by a single space. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.1.4	1	521	5.1.1.2	Verify that any printable Unicode character, including language neutral characters such as spaces and Emojis are permitted in passwords.
	2.1.5	1	620	5.1.1.2	Verify users can change their password.
	2.1.6	1	620	5.1.1.2	Verify that password change functionality requires the user's current and new password.
	2.1.7	1	521	5.1.1.2	Verify that passwords submitted during account registration, login, and password change are checked against a set of breached passwords either locally (such as the top 1,000 or 10,000 most common passwords which match the system's password policy) or using an external API. If using an API a zero knowledge proof or other mechanism should be used to ensure that the plain text password is not sent or used in verifying the breach status of the password. If the password is breached, the application must require the user to set a new non-breached password. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.1.8	1	521	5.1.1.2	Verify that a password strength meter is provided to help users set a stronger password.
	2.1.9	1	521	5.1.1.2	Verify that there are no password composition rules limiting the type of characters permitted. There should be no requirement for upper or lower case or numbers or special characters. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.1.10	1	263	5.1.1.2	Verify that there are no periodic credential rotation or password history requirements.
	2.1.11	1	521	5.1.1.2	Verify that "paste" functionality, browser password helpers, and external password managers are permitted.
	2.1.12	1	521	5.1.1.2	Verify that the user can choose to either temporarily view the entire masked password, or temporarily view the last typed character of the password on platforms that do not have this as built-in functionality.
General Authenticator Requirements	2.2.1	1	307	5.2.2, 5.1.1.2, 5.1.4.2, 5.1.5.2	Verify that anti-automation controls are effective at mitigating breached credential testing, brute force, and account lockout attacks. Such controls include blocking the most common breached passwords, soft lockouts, rate limiting, CAPTCHA, ever increasing delays between attempts, IP address restrictions, or risk-based restrictions such as location, first login on a device, recent attempts to unlock the account, or similar. Verify that no more than 100 failed attempts per hour is possible on a single account.
	2.2.2	1	304	5.2.10	Verify that the use of weak authenticators (such as SMS and email) is limited to secondary verification and transaction approval and not as a replacement for more secure authentication methods. Verify that stronger methods are offered before weak methods, users are aware of the risks, or that proper measures are in place to limit the risks of account compromise.
	2.2.3	1	620		Verify that secure notifications are sent to users after updates to authentication details, such as credential resets, email or address changes, logging in from unknown or risky locations. The use of push notifications - rather than SMS or email - is preferred, but in the absence of push notifications, SMS or email is acceptable as long as no sensitive information is disclosed in the notification.
	2.2.4	3	308	5.2.5	Verify impersonation resistance against phishing, such as the use of multi-factor authentication, cryptographic devices with intent (such as connected keys with a push to authenticate), or at higher AAL levels, client-side certificates.
	2.2.5	3	319	5.2.6	Verify that where a Credential Service Provider (CSP) and the application verifying authentication are separated, mutually authenticated TLS is in place between the two endpoints.
	2.2.6	3	308	5.2.8	Verify replay resistance through the mandated use of One-time Passwords (OTP) devices, cryptographic authenticators, or lookup codes.
	2.2.7	3	308	5.2.9	Verify intent to authenticate by requiring the entry of an OTP token or user-initiated action such as a button press on a FIDO hardware key.
Authenticator Lifecycle Requirements	2.3.1	1	330	5.1.1.2, A. 3	Verify system generated initial passwords or activation codes SHOULD be securely randomly generated, SHOULD be at least 6 characters long, and MAY contain letters and numbers, and expire after a short period of time. These initial secrets must not be permitted to become the long term password.
	2.3.2	2	308	6.1.3	Verify that enrollment and use of subscriber-provided authentication devices are supported, such as a U2F or FIDO tokens.
	2.3.3	2	287	6.1.4	Verify that renewal instructions are sent with sufficient time to renew time bound authenticators.
Credentials Storage Credentials	2.4.1	2	916	5.1.1.2	Verify that passwords are stored in a form that is resistant to offline attacks. Passwords SHALL be salted and hashed using an approved one-way key derivation or password hashing function. Key derivation and password hashing functions take a password, a salt, and a cost factor as inputs when generating a password hash. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.4.2	2	916	5.1.1.2	Verify that the salt is at least 32 bits in length and be chosen arbitrarily to minimize salt value collisions among stored hashes. For each credential, a unique salt value and the resulting hash SHALL be stored. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.4.3	2	916	5.1.1.2	Verify that if PBKDF2 is used, the iteration count SHOULD be as large as verification server performance will allow, typically at least 100,000 iterations. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.4.4	2	916	5.1.1.2	Verify that if bcrypt is used, the work factor SHOULD be as large as verification server performance will allow, typically at least 13. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.4.5	2	916	5.1.1.2	Verify that an additional iteration of a key derivation function is performed, using a salt value that is secret and known only to the verifier. Generate the salt value using an approved random bit generator [SP 800-90Ar1] and provide at least the minimum security strength specified in the latest revision of SP 800-131A. The secret salt value SHALL be stored separately from the hashed passwords (e.g., in a specialized device like a hardware security module).
Credential Recovery Requirements	2.5.1	1	640	5.1.1.2	Verify that a system generated initial activation or recovery secret is not sent in clear text to the user. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.5.2	1	640	5.1.1.2	Verify password hints or knowledge-based authentication (so-called "secret questions") are not present.
	2.5.3	1	640	5.1.1.2	Verify password credential recovery does not reveal the current password in any way. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.5.4	1	16	5.1.1.2, A. 3	Verify shared or default accounts are not present (e.g. "root", "admin", or "sa").
	2.5.5	1	304	6.1.2.3	Verify that if an authentication factor is changed or replaced, that the user is notified of this event.
	2.5.6	1	640	5.1.1.2	Verify forgotten password, and other recovery paths use a secure recovery mechanism, such as time-based OTP (TOTP) or other soft token, mobile push, or another offline recovery mechanism. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))
	2.5.7	2	308	6.1.2.3	Verify that if OTP or multi-factor authentication factors are lost, that evidence of identity proofing is performed at the same level as during enrollment.
Look-up Secret Verifier Requirements	2.6.1	2	308	5.1.2.2	Verify that lookup secrets can be used only once.
	2.6.2	2	330	5.1.2.2	Verify that lookup secrets have sufficient randomness (112 bits of entropy), or if less than 112 bits of entropy, salted with a unique and random 32-bit salt and hashed with an approved one-way hash.
	2.6.3	2	310	5.1.2.2	Verify that lookup secrets are resistant to offline attacks, such as predictable values.
Out of Band Verifier Requirements	2.7.1	1	287	5.1.3.2	Verify that clear text out of band (NIST "restricted") authenticators, such as SMS or PSTN, are not offered by default, and stronger alternatives such as push notifications are offered first.
	2.7.2	1	287	5.1.3.2	Verify that the out of band verifier expires out of band authentication requests, codes, or tokens after 10 minutes.
	2.7.3	1	287	5.1.3.2	Verify that the out of band verifier authentication requests, codes, or tokens are only usable once, and only for the original authentication request.
	2.7.4	1	523	5.1.3.2	Verify that the out of band authenticator and verifier communicates over a secure independent channel.
	2.7.5	2	256	5.1.3.2	Verify that the out of band verifier retains only a hashed version of the authentication code.
	2.7.6	2	310	5.1.3.2	Verify that the initial authentication code is generated by a secure random number generator, containing at least 20 bits of entropy (typically a six digital random number is sufficient).
Single or Multi Factor One Time Verifier Requirements	2.8.1	1	613	5.1.4.2, 5.1.5.2	Verify that time-based OTPs have a defined lifetime before expiring.
	2.8.2	2	320	5.1.4.2, 5.1.5.2	Verify that symmetric keys used to verify submitted OTPs are highly protected, such as by using a hardware security module or secure operating system based key storage.
	2.8.3	2	326	5.1.4.2, 5.1.5.2	Verify that approved cryptographic algorithms are used in the generation, seeding, and verification of OTPs.
	2.8.4	2	287	5.1.4.2, 5.1.5.2	Verify that time-based OTP can be used only once within the validity period.
	2.8.5	2	287	5.1.5.2	Verify that if a time-based multi-factor OTP token is re-used during the validity period, it is logged and rejected with secure notifications being sent to the holder of the device.
	2.8.6	2	613	5.2.1	Verify physical single-factor OTP generator can be revoked in case of theft or other loss. Ensure that revocation is immediately effective across logged in sessions, regardless of location.
	2.8.7	3	308	5.2.3	Verify that biometric authenticators are limited to use only as secondary factors in conjunction with either something you have and something you know.
Cryptographic Software and Devices Verifier Requirements	2.9.1	2	320	5.1.7.2	Verify that cryptographic keys used in verification are stored securely and protected against disclosure, such as using a Trusted Platform Module (TPM) or Hardware Security Module (HSM), or an OS service that can use this secure storage.
	2.9.2	2	330	5.1.7.2	Verify that the challenge nonce is at least 64 bits in length, and statistically unique or unique over the lifetime of the cryptographic device.
	2.9.3	2	327	5.1.7.2	Verify that approved cryptographic algorithms are used in the generation, seeding, and verification.
Service Authentication Requirements	2.10.1	LVL2: OS assisted, LVL3: HSM	287	5.1.1.1	Verify that intra-service secrets do not rely on unchanging credentials such as passwords, API keys or shared accounts with privileged access.
	2.10.2	LVL2: OS assisted, LVL3: HSM	255	5.1.1.1	Verify that if passwords are required for service authentication, the service account used is not a default credential. (e.g. root/root or admin/admin are default in some services during installation).
	2.10.3	LVL2: OS assisted, LVL3: HSM	522	5.1.1.1	Verify that passwords are stored with sufficient protection to prevent offline recovery attacks, including local system access.
	2.10.4	LVL2: OS assisted, LVL3: HSM	798		Verify passwords, integrations with databases and third-party systems, seeds and internal secrets, and API keys are managed securely and not included in the source code or stored within source code repositories. Such storage SHOULD resist offline attacks. The use of a secure software key store (L1), hardware TPM, or an HSM (L3) is recommended for password storage.

&A

Page &P

Session_Management

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Fundamental Session Management Requirements	3.1.1	1	598		Verify the application never reveals session tokens in URL parameters or error messages.	Valid	Testing phase	Burp Suite	Yes	Yes	URL parameters are kind of GET parameters which is a bad idea to store it in a url because attacker can easily read it through the screeen
Session Binding Requirements	3.2.1	1	384	7.1	Verify the application generates a new session token on user authentication. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))	Valid	Development phase	Nessus	Yes	No	Sessions are unique to each person so it can not be shared to anyone.
	3.2.2	1	331	7.1	Verify that session tokens possess at least 64 bits of entropy. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))	Non-valid	Design	none	No	No	If a session ID uses 64bit entropy, it will take lots of time for attacker to guess.
	3.2.3	1	539	7.1	Verify the application only stores session tokens in the browser using secure methods such as appropriately secured cookies (see section 3.4) or HTML 5 session storage.	Valid	Implementation phase	Nmap	Yes	Yes	Because of the risk of cross-site scripting (XSS) attacks, secrets used for session binding Can NOT be stored in vulnerable locations such as HTML5 Local Storage.
	3.2.4	2	331	7.1	Verify that session token are generated using approved cryptographic algorithms. ([C6](https://www.owasp.org/index.php/OWASP_Proactive_Controls#tab=Formal_Numbering))	Valid	Development	Nessus	Yes	Yes
Session Logout and Timeout Requirements	3.3.1	1	613	7.1	Verify that logout and expiration invalidate the session token, such that the back button or a downstream relying party does not resume an authenticated session, including across relying parties. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	testing phase	Kali	Yes	No	Did During lab
	3.3.2	1	613	7.2	If authenticators permit users to remain logged in, verify that re-authentication occurs periodically both when actively used or after an idle period. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering)) * L1: 30 days * L2: 12 hours or 30 minutes of inactivity, 2FA optional * L3: 12 hours or 15 minutes of inactivity, with 2FA	Valid	testing phase	Burp Suite	No	Yes
	3.3.3	2	613		Verify that the application gives the option to terminate all other active sessions after a successful password change (including change via password reset/recovery), and that this is effective across the application, federated login (if present), and any relying parties.	Valid	Design	Nessus	No	No	Honeypot and logic lockdoown
	3.3.4	2	613	7.1	Verify that users are able to view and (having re-entered login credentials) log out of any or all currently active sessions and devices.	Valid	Development	Nmap	Yes	Yes	Implemented during lab
Cookie-based Session Management	3.4.1	1	614	7.1.1	Verify that cookie-based session tokens have the 'Secure' attribute set. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Testing phase	Burp Suite	Yes	Yes	Was not taken into consideration during any stage of the development
	3.4.2	1	1004	7.1.1	Verify that cookie-based session tokens have the 'HttpOnly' attribute set. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	26	Kali	Yes	Yes	Verified through wp-config.php file and configuration settings
	3.4.3	1	16	7.1.1	Verify that cookie-based session tokens utilize the 'SameSite' attribute to limit exposure to cross-site request forgery attacks. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Development	Nessus	Yes	Yes	Verified through software documentation
	3.4.4	1	16	7.1.1	Verify that cookie-based session tokens use "__Host-" prefix (see references) to provide session cookie confidentiality.	Valid	Implementation phase	none	Yes	Yes	Verified through wp-config.php file and configuration settings
	3.4.5	1	16	7.1.1	Verify that if the application is published under a domain name with other applications that set or use session cookies that might override or disclose the session cookies, set the path attribute in cookie-based session tokens using the most precise path possible. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))	Not Applicable	Design	Kali	Yes	Yes	Didn’t considered
Token-based Session Management	3.5.1	2	290	7.1.2	Verify the application allows users to revoke OAuth tokens that form trust relationships with linked applications.	Non-valid	Implementation phase	Nmap	Yes	Yes	N/A
	3.5.2	2	798		Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.	Non-valid	Testing phase	Burp Suite	Yes	Yes	N/A
	3.5.3	2	345		Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null cipher, and key substitution attacks.	Valid	Testing phase	Nessus	Yes	Yes	Implemented during lab
Re-authentication from a Federation or Assertion	3.6.1	3	613	7.2.1	Verify that relying parties specify the maximum authentication time to Credential Service Providers (CSPs) and that CSPs re-authenticate the subscriber if they haven't used a session within that period.	Valid	Requirement	none	Yes	Yes
	3.6.2	3	613	7.2.1	Verify that Credential Service Providers (CSPs) inform Relying Parties (RPs) of the last authentication event, to allow RPs to determine if they need to re-authenticate the user.	Non-valid	Requirement	none	Yes	Yes	N/A
Defenses Against Session Management Exploits	3.7.1	1	778		Verify the application ensures a valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions or account modifications.	Valid	Design	Nessus	No	Yes	All in one firewall plugin

&A

Page &P

Access_Control

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
General Access Control Design	4.1.1	1	602		Verify that the application enforces access control rules on a trusted service layer, especially if client-side access control is present and could be bypassed.	Valid	Implementation Phase	None	Yes	Yes	Bypassing security can lead to unauthorized access
	4.1.2	1	639		Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized.	Valid	Testing Phase	Nessus	Yes	Yes	was taken care of during testing phase
	4.1.3	1	285		Verify that the principle of least privilege exists - users should only be able to access functions, data files, URLs, controllers, services, and other resources, for which they possess specific authorization. This implies protection against spoofing and elevation of privilege. ([C7](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Designing Phase	DVWA	Yes	Yes	enabled honeypot to main principle.
	4.1.4	1	276		Verify that the principle of deny by default exists whereby new users/roles start with minimal or no permissions and users/roles do not receive access to new features until access is explicitly assigned. ([C7](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid		None	No	No	did not considered
	4.1.5	1	285		Verify that access controls fail securely including when an exception occurs. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Implementation Phase	Nessus	Yes	Yes	was taken care of during testing phase
Operation Level Access Control	4.2.1	1	639		Verify that sensitive data and APIs are protected against Insecure Direct Object Reference (IDOR) attacks targeting creation, reading, updating and deletion of records, such as creating or updating someone else's record, viewing everyone's records, or deleting all records.	Non-valid	Designing and development stage	None	Yes	No	did not considered
	4.2.2	1	352		Verify that the application or framework enforces a strong anti-CSRF mechanism to protect authenticated functionality, and effective anti-automation or anti-CSRF protects unauthenticated functionality.	Not Applicable	Planning and designing stage	Kali	No	No
Other Access Control Considerations	4.3.1	1	419		Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use.	Valid	Implementation stage	Nessus	Yes	Yes	More layers of authentication makes it robust
	4.3.2	1	548		Verify that directory browsing is disabled unless deliberately desired. Additionally, applications should not allow discovery or disclosure of file or directory metadata, such as Thumbs.db, .DS_Store, .git or .svn folders.	Valid	Designing stage	Kali	Yes	Yes	Disabled directory
	4.3.3	2	732		Verify the application has additional authorization (such as step up or adaptive authentication) for lower value systems, and / or segregation of duties for high value applications to enforce anti-fraud controls as per the risk of application and past fraud.	Valid	Testing stage		Yes	Yes	did not considered

&A

Page &P

Input_Validation

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)
Input Validation Requirements	5.1.1	1	235		Verify that the application has defenses against HTTP parameter pollution attacks, particularly if the application framework makes no distinction about the source of request parameters (GET, POST, cookies, headers, or environment variables).	Valid	Implementation stage	None	Yes	yes	Protect data every where
	5.1.2	1	915		Verify that frameworks protect against mass parameter assignment attacks, or that the application has countermeasures to protect against unsafe parameter assignment, such as marking fields private or similar. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Development stage	None	Yes	yes	Access controls
	5.1.3	1	20		Verify that all input (HTML form fields, REST requests, URL parameters, HTTP headers, cookies, batch files, RSS feeds, etc) is validated using positive validation (allow lists). ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Testing stage	None	yes	Yes	validate all inputs
	5.1.4	1	20		Verify that structured data is strongly typed and validated against a defined schema including allowed characters, length and pattern (e.g. credit card numbers or telephone, or validating that two related fields are reasonable, such as checking that suburb and zip/postcode match). ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Development stage	Nessus	yes	yes	Check for the valid input
	5.1.5	1	601		Verify that URL redirects and forwards only allow destinations which appear on an allow list, or show a warning when redirecting to potentially untrusted content.	Valid	Testing stage		yes	yes	Enforcing active controls
Sanitization and Sandboxing Requirements	5.2.1	1	116		Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized with an HTML sanitizer library or framework feature. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	Designing and development stage	none	No	No	none
	5.2.2	1	138		Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length.	Valid	Planning and designing stage	Nessus	yes	yes	Security handling by proper encryption
	5.2.3	1	147		Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection.	Valid	Implementation stage	Kali	Yes	Yes	Penetration testing conducted in labs
	5.2.4	1	95		Verify that the application avoids the use of eval() or other dynamic code execution features. Where there is no alternative, any user input being included must be sanitized or sandboxed before being executed.	Valid	Designing stage	None	Yes	Yes	Secure data access
	5.2.5	1	94		Verify that the application protects against template injection attacks by ensuring that any user input being included is sanitized or sandboxed.	Valid	Testing stage	None	Yes	Yes	Tests conducted during lab
	5.2.6	1	918		Verify that the application protects against SSRF attacks, by validating or sanitizing untrusted data or HTTP file metadata, such as filenames and URL input fields, and uses allow lists of protocols, domains, paths and ports.	Not Applicable	Does not apply	Does not apply	Does not apply	Does not apply	None
	5.2.7	1	159		Verify that the application sanitizes, disables, or sandboxes user-supplied Scalable Vector Graphics (SVG) scriptable content, especially as they relate to XSS resulting from inline scripts, and foreignObject.	Valid	Development stage	kali	Yes	Yes	Tests conducted during lab
	5.2.8	1	94		Verify that the application sanitizes, disables, or sandboxes user-supplied scriptable or expression template language content, such as Markdown, CSS or XSL stylesheets, BBCode, or similar.	Valid	Deployment stage	None	Yes	Yes	Security handling by proper encryption
Output encoding and Injection Prevention Requirements	5.3.1	1	116		Verify that output encoding is relevant for the interpreter and context required. For example, use encoders specifically for HTML values, HTML attributes, JavaScript, URL parameters, HTTP headers, SMTP, and others as the context requires, especially from untrusted inputs (e.g. names with Unicode or apostrophes, such as ねこ or O'Hara). ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	Coding stage	None	No	No	none
	5.3.2	1	176		Verify that output encoding preserves the user's chosen character set and locale, such that any Unicode character point is valid and safely handled. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Designing and development stage	None	Yes	Yes	Intruder parameters are used
	5.3.3	1	79		Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM based XSS. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Testing stage	Kali	Yes	Yes	Penetration testing conducted in labs
	5.3.4	1	89		Verify that data selection or database queries (e.g. SQL, HQL, ORM, NoSQL) use parameterized queries, ORMs, entity frameworks, or are otherwise protected from database injection attacks. ([C3](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	Maintainence stage	None	No	No	None
	5.3.5	1	89		Verify that where parameterized or safer mechanisms are not present, context-specific output encoding is used to protect against injection attacks, such as the use of SQL escaping to protect against SQL injection. ([C3, C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Testing and designing stage	kali	Yes	Yes	Implementing better data base access
	5.3.6	1	830		Verify that the application protects against JavaScript or JSON injection attacks, including for eval attacks, remote JavaScript includes, Content Security Policy (CSP) bypasses, DOM XSS, and JavaScript expression evaluation. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	testing stage	kali	yes	yes	Secure handled of data by proper encryption
	5.3.7	1	943		Verify that the application protects against LDAP injection vulnerabilities, or that specific security controls to prevent LDAP injection have been implemented. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Not Applicable	Does not apply	Does not apply	Does not apply	Does not apply	None
	5.3.8	1	78		Verify that the application protects against OS command injection and that operating system calls use parameterized OS queries or use contextual command line output encoding. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	testing stage	kali	yes	yes	Penetration testing conducted in labs
	5.3.9	1	829		Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks.	Valid	Designing and testing stage	None	Yes	Yes	Access controls
	5.3.10	1	643		Verify that the application protects against XPath injection or XML injection attacks. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Testing and development stage	None	Yes	Yes	Penetration testing conducted in labs
Memory, String and Unmanaged Code Requirements	5.4.1	2	120		Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows.	Valid	Planning and designing stage	None	Yes	yes	Security handled with ASVS controls
	5.4.2	2	134		Verify that format strings do not take potentially hostile input, and are constant.	Valid	Implementation stage	None	yes	Yes	Protect data everywhere
	5.4.3	2	190		Verify that sign, range, and input validation techniques are used to prevent integer overflows.	Valid	Development stage	None	Yes	Yes	protect data everywhere
Deserialization Prevention Requirements	5.5.1	1	502		Verify that serialized objects use integrity checks or are encrypted to prevent hostile object creation or data tampering. ([C5](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Deployment stage	None	Yes	Yes	validate all inputs
	5.5.2	1	611		Verify that the application correctly restricts XML parsers to only use the most restrictive configuration possible and to ensure that unsafe features such as resolving external entities are disabled to prevent XML eXternal Entity (XXE) attacks.	Valid	Designing stage	None	Yes	Yes	Validate all inputs
	5.5.3	1	502		Verify that deserialization of untrusted data is avoided or is protected in both custom code and third-party libraries (such as JSON, XML and YAML parsers).	Valid	Designing stage	None	Yes	Yes	Security controls
	5.5.4	1	95		Verify that when parsing JSON in browsers or JavaScript-based backends, JSON.parse is used to parse the JSON document. Do not use eval() to parse JSON.	Non-valid	Designing stage	None	No	No	None

&A

Page &P

Cryptography_at_Rest

Area	#	ASVS Level	CWE	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Data Classification	6.1.1	2	311	Verify that regulated private data is stored encrypted while at rest, such as Personally Identifiable Information (PII), sensitive personal information, or data assessed likely to be subject to EU's GDPR.	Non-valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Was not taken into consideration during any stage of the development
	6.1.2	2	311	Verify that regulated health data is stored encrypted while at rest, such as medical records, medical device details, or de-anonymized research records.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	6.1.3	2	311	Verify that regulated financial data is stored encrypted while at rest, such as financial accounts, defaults or credit history, tax records, pay history, beneficiaries, or de-anonymized market or research records.	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Was not taken into consideration during any stage of the development
Algorithms	6.2.1	1	310	Verify that all cryptographic modules fail securely, and errors are handled in a way that does not enable Padding Oracle attacks.	Valid	DEVELOPMENT AND TEST STAGES	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE, QUALYS	YES	YES	Verified through wp-config.php file and configuration settings
	6.2.2	2	327	Verify that industry proven or government approved cryptographic algorithms, modes, and libraries are used, instead of custom coded cryptography. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DESIGN	NONE	YES	YES	Verified through software documentation
	6.2.3	2	326	Verify that encryption initialization vector, cipher configuration, and block modes are configured securely using the latest advice.	Valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Verified through wp-config.php file and configuration settings
	6.2.4	2	326	Verify that random number, encryption or hashing algorithms, key lengths, rounds, ciphers or modes, can be reconfigured, upgraded, or swapped at any time, to protect against cryptographic breaks. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Verified through wp-config.php file and configuration settings
	6.2.5	2	326	Verify that known insecure block modes (i.e. ECB, etc.), padding modes (i.e. PKCS#1 v1.5, etc.), ciphers with small block sizes (i.e. Triple-DES, Blowfish, etc.), and weak hashing algorithms (i.e. MD5, SHA1, etc.) are not used unless required for backwards compatibility.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Verified through wp-config.php file and configuration settings
	6.2.6	2	326	Verify that nonces, initialization vectors, and other single use numbers must not be used more than once with a given encryption key. The method of generation must be appropriate for the algorithm being used.	Non-valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Verified through wp-config.php file and configuration settings that keys for nonce are static
	6.2.7	3	326	Verify that encrypted data is authenticated via signatures, authenticated cipher modes, or HMAC to ensure that ciphertext is not altered by an unauthorized party.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	6.2.8	3	385	Verify that all cryptographic operations are constant-time, with no 'short-circuit' operations in comparisons, calculations, or returns, to avoid leaking information.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Random values	6.3.1	2	338	Verify that all random numbers, random file names, random GUIDs, and random strings are generated using the cryptographic module's approved cryptographically secure random number generator when these random values are intended to be not guessable by an attacker.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Yes, comes standard with Ubuntu installations
	6.3.2	2	338	Verify that random GUIDs are created using the GUID v4 algorithm, and a Cryptographically-secure Pseudo-random Number Generator (CSPRNG). GUIDs created using other pseudo-random number generators may be predictable.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Yes, comes standard with Ubuntu installations
	6.3.3	3	338	Verify that random numbers are created with proper entropy even when the application is under heavy load, or that the application degrades gracefully in such circumstances.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Secret Management	6.4.1	2	798	Verify that a secrets management solution such as a key vault is used to securely create, store, control access to and destroy secrets. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Was not implemented
	6.4.2	2	320	Verify that key material is not exposed to the application but instead uses an isolated security module like a vault for cryptographic operations. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Was not implemented

&A

Page &P

Error_Handling_and_Logging

Area	#	ASVS Level	CWE	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Log Content Requirements	7.1.1	1	532	Verify that the application does not log credentials or payment details. Session tokens should only be stored in logs in an irreversible, hashed form. ([C9, C10](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Verified through software and plugin documentation
	7.1.2	1	532	Verify that the application does not log other sensitive data as defined under local privacy laws or relevant security policy. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Yes, this is verified through software and plugin documentation for WordPress, associated plugins and backend software. In addition Jetpack logging is EU GDPR compliant
	7.1.3	2	778	Verify that the application logs security relevant events including successful and failed authentication events, access control failures, deserialization failures and input validation failures. ([C5, C7](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NONE	YES	NO	Jetpack and WP-All-in-One Security and Firewall plugins provide logging for all core wordpress changes and failed account accesses
	7.1.4	2	778	Verify that each log event includes necessary information that would allow for a detailed investigation of the timeline when an event happens. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NONE	YES	YES	Yes, Jetpack and WP-All-in-One Security and Firewall Plugin do this and is reported as such on their respective websites
Log Processing Requirements	7.2.1	2	778	Verify that all authentication decisions are logged, without storing sensitive session identifiers or passwords. This should include requests with relevant metadata needed for security investigations.	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NONE	YES	YES	Yes, WP-All-in-One Security and Firewall does this and Jetpack logging is EU GDPR compliant
	7.2.2	2	285	Verify that all access control decisions can be logged and all failed decisions are logged. This should include requests with relevant metadata needed for security investigations.	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NONE	YES	YES	Yes, Jetpack and WP-All-in-One Security and Firewall Plugin do this and is reported as such on their respective websites
Log Protection Requirements	7.3.1	2	117	Verify that the application appropriately encodes user-supplied data to prevent log injection. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NESSUS, KALI LINUX/METASPLOIT	YES	NO	Yes, the latest version of Jetpack, WordPress and WP All-in-One Security and Firewall all are protected from known injection attacks (Confirmed from CVE analysis from latest version of software)
	7.3.2	2	117	Verify that all events are protected from injection when viewed in log viewing software. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NONE	NO	NO	Not enabled in the firewall setting in WP All-in-One Security and Firewall
	7.3.3	2	200	Verify that security logs are protected from unauthorized access and modification. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	YES	NO	Prevented through setting in WP All-in-One Security and Firewall Plugin
	7.3.4	2		Verify that time sources are synchronized to the correct time and time zone. Strongly consider logging only in UTC if systems are global to assist with post-incident forensic analysis. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT,TEST, AND MAINTENANCE STAGES	NONE	YES	NO	Verified through software and plugin documentation
Error Handling	7.4.1	1	210	Verify that a generic message is shown when an unexpected or security sensitive error occurs, potentially with a unique ID which support personnel can use to investigate. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Jetpack plugin provides logging for all core wordpress changes as well, WP All-in-One Security and Firewall Plugin also provide detailed logs
	7.4.2	2	544	Verify that exception handling (or a functional equivalent) is used across the codebase to account for expected and unexpected error conditions. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	7.4.3	2	431	Verify that a "last resort" error handler is defined which will catch all unhandled exceptions. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY

&A

Page &P

Data_Protection

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	Source Code Reference	Comment	Tool Used
General Data Protection	8.1.1	2	524		Verify the application protects sensitive data from being cached in server components such as load balancers and application caches.
	8.1.2	2	524		Verify that all cached or temporary copies of sensitive data stored on the server are protected from unauthorized access or purged/invalidated after the authorized user accesses the sensitive data.
	8.1.3	2	233		Verify the application minimizes the number of parameters in a request, such as hidden fields, Ajax variables, cookies and header values.
	8.1.4	2	770		Verify the application can detect and alert on abnormal numbers of requests, such as by IP, user, total per hour or day, or whatever makes sense for the application.
	8.1.5	3	19		Verify that regular backups of important data are performed and that test restoration of data is performed.
	8.1.6	3	19		Verify that backups are stored securely to prevent data from being stolen or corrupted.
Client-side Data Protection	8.2.1	1	525		Verify the application sets sufficient anti-caching headers so that sensitive data is not cached in modern browsers.
	8.2.2	1	922		Verify that data stored in browser storage (such as HTML5 local storage, session storage, IndexedDB, or cookies) does not contain sensitive data or PII.
	8.2.3	1	922		Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated.
Sensitive Private Data	8.3.1	1	319		Verify that sensitive data is sent to the server in the HTTP message body or headers, and that query string parameters from any HTTP verb do not contain sensitive data.
	8.3.2	1	212		Verify that users have a method to remove or export their data on demand.
	8.3.3	1	285		Verify that users are provided clear language regarding collection and use of supplied personal information and that users have provided opt-in consent for the use of that data before it is used in any way.
	8.3.4	1	200		Verify that all sensitive data created and processed by the application has been identified, and ensure that a policy is in place on how to deal with sensitive data. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))
	8.3.5	2	532		Verify accessing sensitive data is audited (without logging the sensitive data itself), if the data is collected under relevant data protection directives or where logging of access is required.
	8.3.6	2	226		Verify that sensitive information contained in memory is overwritten as soon as it is no longer required to mitigate memory dumping attacks, using zeroes or random data.
	8.3.7	2	327		Verify that sensitive or private information that is required to be encrypted, is encrypted using approved algorithms that provide both confidentiality and integrity. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))
	8.3.8	2	285		Verify that sensitive personal information is subject to data retention classification, such that old or out of date data is deleted automatically, on a schedule, or as the situation requires.

&A

Page &P

Communication_Security

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Communications Security Requirements	9.1.1	1	319		Verify that secured TLS is used for all client connectivity, and does not fall back to insecure or unencrypted protocols. ([C8](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	Planning and Testing phase	None	Yes	Yes	Didn’t Considered
	9.1.2	1	326		Verify using online or up to date TLS testing tools that only strong algorithms, ciphers, and protocols are enabled, with the strongest algorithms and ciphers set as preferred.	Non-valid	Designing and development stage	Nessus
	9.1.3	1	326		Verify that old versions of SSL and TLS protocols, algorithms, ciphers, and configuration are disabled, such as SSLv2, SSLv3, or TLS 1.0 and TLS 1.1. The latest version of TLS should be the preferred cipher suite.	Valid	Testing stage	NESSUS, KALI LINUX/METASPLOIT	YES	NO
Server Communications Security Requirements	9.2.1	2	295		Verify that connections to and from the server use trusted TLS certificates. Where internally generated or self-signed certificates are used, the server must be configured to only trust specific internal CAs and specific self-signed certificates. All others should be rejected.	Valid	Implementation stage	NONE	NO	NO
	9.2.2	2	319		Verify that encrypted communications such as TLS is used for all inbound and outbound connections, including for management ports, monitoring, authentication, API, or web service calls, database, cloud, serverless, mainframe, external, and partner connections. The server must not fall back to insecure or unencrypted protocols.	Valid	Designing stage	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE	YES	NO
	9.2.3	2	287		Verify that all encrypted connections to external systems that involve sensitive information or functions are authenticated.	Valid	Testing stage	NONE	YES	NO
	9.2.4	2	299		Verify that proper certification revocation, such as Online Certificate Status Protocol (OCSP) Stapling, is enabled and configured.	Non-valid	Does not apply	None	Yes	Yes
	9.2.5	3	544		Verify that backend TLS connection failures are logged.	Valid	Development stage	NESSUS	Yes	NO

&A

Page &P

Malicious_code

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Code Integrity Controls	10.1.1	3	749		Verify that a code analysis tool is in use that can detect potentially malicious code, such as time functions, unsafe file operations and network connections.	Valid	Analysis stage	None	Yes	Yes	Analysing duirng the labs
Malicious Code Search	10.2.1	2	359		Verify that the application source code and third party libraries do not contain unauthorized phone home or data collection capabilities. Where such functionality exists, obtain the user's permission for it to operate before collecting any data.	Valid	Designing stage	None	Yes	Yes	Active Security controls
	10.2.2	2	272		Verify that the application does not ask for unnecessary or excessive permissions to privacy related features or sensors, such as contacts, cameras, microphones, or location.	Valid	Development and implementation stage	None	Yes	Yes	Security controls
	10.2.3	3	507		Verify that the application source code and third party libraries do not contain back doors, such as hard-coded or additional undocumented accounts or keys, code obfuscation, undocumented binary blobs, rootkits, or anti-debugging, insecure debugging features, or otherwise out of date, insecure, or hidden functionality that could be used maliciously if discovered.	Non-valid	Maintainence stage	None	No	No	N/A
	10.2.4	3	511		Verify that the application source code and third party libraries do not contain time bombs by searching for date and time related functions.	Valid	Designing stage	None	Yes	Yes	Proper encryption of data
	10.2.5	3	511		Verify that the application source code and third party libraries do not contain malicious code, such as salami attacks, logic bypasses, or logic bombs.	Valid	Testing stage	Nessus and kali	Yes	Yes	testing peformed in labs
	10.2.6	3	507		Verify that the application source code and third party libraries do not contain Easter eggs or any other potentially unwanted functionality.	Not Applicable	Does not apply	Does not apply	Does not apply	Does not apply	N/A
Deployed Application Integrity Controls	10.3.1	1	16		Verify that if the application has a client or server auto-update feature, updates should be obtained over secure channels and digitally signed. The update code must validate the digital signature of the update before installing or executing the update.	Valid	Coding stage	None	Yes	Yes	Protect data everywhere
	10.3.2	1	353		Verify that the application employs integrity protections, such as code signing or subresource integrity. The application must not load or execute code from untrusted sources, such as loading includes, modules, plugins, code, or libraries from untrusted sources or the Internet.	Valid	Designing and development stage	None	Yes	Yes	All in one WP security
	10.3.3	1	350		Verify that the application has protection from subdomain takeovers if the application relies upon DNS entries or DNS subdomains, such as expired domain names, out of date DNS pointers or CNAMEs, expired projects at public source code repos, or transient cloud APIs, serverless functions, or storage buckets (autogen-bucket-id.cloud.example.com) or similar. Protections can include ensuring that DNS names used by applications are regularly checked for expiry or change.	Non-valid	Implementation stage	None	No	No	N/A

&A

Page &P

Business_Logic

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Business Logic Security Requirements	11.1.1	1	841		Verify the application will only process business logic flows for the same user in sequential step order and without skipping steps.	Valid	Analysis stage	None	Yes	Yes	Analysing duirng the labs
	11.1.2	1	799		Verify the application will only process business logic flows with all steps being processed in realistic human time, i.e. transactions are not submitted too quickly.	Valid	Designing stage	None	Yes	Yes	Active Security controls
	11.1.3	1	770		Verify the application has appropriate limits for specific business actions or transactions which are correctly enforced on a per user basis.	Valid	Development and implementation stage	None	Yes	Yes	Security controls
	11.1.4	1	770		Verify the application has sufficient anti-automation controls to detect and protect against data exfiltration, excessive business logic requests, excessive file uploads or denial of service attacks.	Valid	Maintainence stage	None	No	No	N/A
	11.1.5	1	841		Verify the application has business logic limits or validation to protect against likely business risks or threats, identified using threat modeling or similar methodologies.	Not Applicable	Designing stage	None	Yes	Yes	Proper encryption of data
	11.1.6	2	367		Verify the application does not suffer from "Time Of Check to Time Of Use" (TOCTOU) issues or other race conditions for sensitive operations.	Valid	Testing stage	Nessus and kali	Yes	Yes	testing peformed in labs
	11.1.7	2	754		Verify the application monitors for unusual events or activity from a business logic perspective. For example, attempts to perform actions out of order or actions which a normal user would never attempt. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	Testing stage	Nessus and kali	Yes	Yes	Analysing duirng the labs
	11.1.8	2	390		Verify the application has configurable alerting when automated attacks or unusual activity is detected.	Valid	Testing stage	Nessus and kali	Yes	Yes	testing peformed in labs

&A

Page &P

Files_and_Resources

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
File Upload Requirements	12.1.1	1	400		Verify that the application will not accept large files that could fill up storage or cause a denial of service.	Valid	Designing stage	None	Yes	Yes	Limitation of the file sizes to reduce the malicious content
	12.1.2	2	409		Verify that compressed files are checked for "zip bombs" - small input files that will decompress into huge files thus exhausting file storage limits.	Valid	Implementation stage	None	Yes	Yes	To validate the input files
	12.1.3	2	770		Verify that a file size quota and maximum number of files per user is enforced to ensure that a single user cannot fill up the storage with too many files, or excessively large files.	Valid	Designing stage	None	Yes	Yes	Enabling of the limited access
File Integrity Requirements	12.2.1	2	434		Verify that files obtained from untrusted sources are validated to be of expected type based on the file's content.	Valid	testing stage	None	Yes	Yes	Protect data everywhere
File Execution Requirements	12.3.1	1	22		Verify that user-submitted filename metadata is not used directly by system or framework filesystems and that a URL API is used to protect against path traversal.	Valid	Testing stage	None	Yes	Yes	Secuirty handled by proper encryption
	12.3.2	1	73		Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure, creation, updating or removal of local files (LFI).	Valid	Development stage	None	Yes	Yes	Access controls
	12.3.3	1	98		Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure or execution of remote files via Remote File Inclusion (RFI) or Server-side Request Forgery (SSRF) attacks.	Valid	Testing stage	Kali	Yes	Yes	Penetration testing
	12.3.4	1	641		Verify that the application protects against Reflective File Download (RFD) by validating or ignoring user-submitted filenames in a JSON, JSONP, or URL parameter, the response Content-Type header should be set to text/plain, and the Content-Disposition header should have a fixed filename.	Non-valid	Development stage	None	No	No	N/A
	12.3.5	1	78		Verify that untrusted file metadata is not used directly with system API or libraries, to protect against OS command injection.	Valid	Testing stage	Kali	Yes	Yes	Testings peformed duirng labs
	12.3.6	2	829		Verify that the application does not include and execute functionality from untrusted sources, such as unverified content distribution networks, JavaScript libraries, node npm libraries, or server-side DLLs.	Valid	Testing stage	None	Yes	Yes	Security handled by proper encryption
File Storage Requirements	12.4.1	1	922		Verify that files obtained from untrusted sources are stored outside the web root, with limited permissions, preferably with strong validation.	Valid	Development stage	None	Yes	Yes	All in one wp security
	12.4.2	1	509		Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload of known malicious content.	Valid	Testing stage	None	Yes	Yes	Protection of data everywhere
File Download Requirements	12.5.1	1	552		Verify that the web tier is configured to serve only files with specific file extensions to prevent unintentional information and source code leakage. For example, backup files (e.g. .bak), temporary working files (e.g. .swp), compressed files (.zip, .tar.gz, etc) and other extensions commonly used by editors should be blocked unless required.	Valid	Designing stage	None	Yes	Yes	Secure data access
	12.5.2	1	434		Verify that direct requests to uploaded files will never be executed as HTML/JavaScript content.	Valid	Implementation stage	None	Yes	Yes	Access controls
SSRF Protection Requirements	12.6.1	1	918		Verify that the web or application server is configured with an allow list of resources or systems to which the server can send requests or load data/files from.	Valid	Designing stage	None	Yes	Yes	Secuirty control methods

&A

Page &P

Web_Services

Area	#	ASVS Level	CWE	NIST	Verification Requirement	Valid	Source Code Reference	Comment	Tool Used
Generic Web Service Security Verification Requirements	13.1.1	1	116		Verify that all application components use the same encodings and parsers to avoid parsing attacks that exploit different URI or file parsing behavior that could be used in SSRF and RFI attacks.
	13.1.2	1	419		Verify that access to administration and management functions is limited to authorized administrators.
	13.1.3	1	598		Verify API URLs do not expose sensitive information, such as the API key, session tokens etc.
	13.1.4	2	285		Verify that authorization decisions are made at both the URI, enforced by programmatic or declarative security at the controller or router, and at the resource level, enforced by model-based permissions.
	13.1.5	2	434		Verify that requests containing unexpected or missing content types are rejected with appropriate headers (HTTP response status 406 Unacceptable or 415 Unsupported Media Type).
RESTful Web Service Verification Requirements	13.2.1	1	650		Verify that enabled RESTful HTTP methods are a valid choice for the user or action, such as preventing normal users using DELETE or PUT on protected API or resources.
	13.2.2	1	20		Verify that JSON schema validation is in place and verified before accepting input.
	13.2.3	1	352		Verify that RESTful web services that utilize cookies are protected from Cross-Site Request Forgery via the use of at least one or more of the following: double submit cookie pattern, CSRF nonces, or Origin request header checks.
	13.2.4	2	770		Verify that REST services have anti-automation controls to protect against excessive calls, especially if the API is unauthenticated.
	13.2.5	2	436		Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/json.
	13.2.6	2	345		Verify that the message headers and payload are trustworthy and not modified in transit. Requiring strong encryption for transport (TLS only) may be sufficient in many cases as it provides both confidentiality and integrity protection. Per-message digital signatures can provide additional assurance on top of the transport protections for high-security applications but bring with them additional complexity and risks to weigh against the benefits.
SOAP Web Service Verification Requirements	13.3.1	1	20		Verify that XSD schema validation takes place to ensure a properly formed XML document, followed by validation of each input field before any processing of that data takes place.
	13.3.2	2	345		Verify that the message payload is signed using WS-Security to ensure reliable transport between client and service.
GraphQL and other Web Service Data Layer Security Requirements	13.4.1	2	770		Verify that a query allow list or a combination of depth limiting and amount limiting is used to prevent GraphQL or data layer expression Denial of Service (DoS) as a result of expensive, nested queries. For more advanced scenarios, query cost analysis should be used.
	13.4.2	2	285		Verify that GraphQL or other data layer authorization logic should be implemented at the business logic layer instead of the GraphQL layer.

&A

Page &P

Configuration

Area	#	ASVS Level	CWE	Verification Requirement	Valid	SDLC STAGE CONSIDERED	Security Weaknesses As Determined by the Vulnerability & Penetration Assessment Tool -KALI/NESSUS/BURPSUITE/NMAP	Technical - Technological Impact Assessment – Did you Consider the Secure Coding Practices?	Business Impact – Business logic (Functionalities and assurances bult into your website to perfom E-Commerce)	Assessment (Identifiation, Analysis & Reporting) & Comments
Build	14.1.1	2		Verify that the application build and deployment processes are performed in a secure and repeatable way, such as CI / CD automation, automated configuration management, and automated deployment scripts.	Non-valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Was not implemented, but could be created for future stages of SDLC
	14.1.2	2	120	Verify that compiler flags are configured to enable all available buffer overflow protections and warnings, including stack randomization, data execution prevention, and to break the build if an unsafe pointer, memory, format string, integer, or string operations are found.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	14.1.3	2	16	Verify that server configuration is hardened as per the recommendations of the application server and frameworks in use.	Valid	EVERY STAGE	NESSUS, KALI LINUX/METASPLOIT, BURPSUITE, QUALYS	YES	YES	Done over the entirety of the project
	14.1.4	2		Verify that the application, configuration, and all dependencies can be re-deployed using automated deployment scripts, built from a documented and tested runbook in a reasonable time, or restored from backups in a timely fashion.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Yes, documentation does exist to help streamline reinstallation procedures
	14.1.5	3		Verify that authorized administrators can verify the integrity of all security-relevant configurations to detect tampering.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
Dependency	14.2.1	1	1026	Verify that all components are up to date, preferably using a dependency checker during build or compile time. ([C2](https://owasp.org/www-project-proactive-controls/#div-numbering))	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY
	14.2.2	1	1002	Verify that all unneeded features, documentation, samples, configurations are removed, such as sample applications, platform documentation, and default or example users.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Yes, manually or automatically removed during the hardening process
	14.2.3	1	829	Verify that if application assets, such as JavaScript libraries, CSS stylesheets or web fonts, are hosted externally on a content delivery network (CDN) or external provider, Subresource Integrity (SRI) is used to validate the integrity of the asset.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Handled by JetPack Plugin
	14.2.4	2	829	Verify that third party components come from pre-defined, trusted and continually maintained repositories. ([C2](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	All packages downloaded come from either the Trusted WordPress Store Front or from valid and vetted repositories
	14.2.5	2		Verify that an inventory catalog is maintained of all third party libraries in use. ([C2](https://owasp.org/www-project-proactive-controls/#div-numbering))	Valid	DESIGN, DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Yes, Lab documentation validates and specifies usage of 3rd party applications
	14.2.6	2	265	Verify that the attack surface is reduced by sandboxing or encapsulating third party libraries to expose only the required behaviour into the application. ([C2](https://owasp.org/www-project-proactive-controls/#div-numbering))	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	No sandboxing or encapsulation was done
Unintended Security Disclosure Requirements	14.3.1	1	209	Verify that web or application server and framework error messages are configured to deliver user actionable, customized responses to eliminate any unintended security disclosures.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	YES	Yes, this is verified through software and plugin documentation for WordPress, associated plugins and backend software. In addition Jetpack logging is EU GDPR compliant
	14.3.2	1	497	Verify that web or application server and application framework debug modes are disabled in production to eliminate debug features, developer consoles, and unintended security disclosures.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Yes these were disabled during hardening and reported in WP Admin Panel if any were enabled to be disabled
	14.3.3	1	200	Verify that the HTTP headers or any part of the HTTP response do not expose detailed version information of system components.	Valid	DEVELOPMENT AND TEST STAGES	NESSUS	YES	NO	Yes these were disabled during hardening
HTTP Security Headers Requirements	14.4.1	1	173	Verify that every HTTP response contains a Content-Type header. text/*, */*+xml and application/xml content types should also specify a safe character set (e.g., UTF-8, ISO-8859-1).	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Verified through manual review of each webpage
	14.4.2	1	116	Verify that all API responses contain Content-Disposition: attachment; filename="api.json" header (or other appropriate filename for the content type).	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Verified through manual review of each webpage
	14.4.3	1	1021	Verify that a Content Security Policy (CSP) response header is in place that helps mitigate impact for XSS attacks like HTML, DOM, JSON, and JavaScript injection vulnerabilities.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Done by specifying X-Content-Security-Policy in SSL File for HTTP Header contents for Apache. Set to nosniff so that it is not present on front end
	14.4.4	1	116	Verify that all responses contain a X-Content-Type-Options: nosniff header.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Done by specifying X-Content-Security-Policy in SSL File for HTTP Header contents for Apache. Set to nosniff so that it is not present on front end
	14.4.5	1	523	Verify that a Strict-Transport-Security header is included on all responses and for all subdomains, such as Strict-Transport-Security: max-age=15724800; includeSubdomains.	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Not done, but can be configured later
	14.4.6	1	116	Verify that a suitable "Referrer-Policy" header is included, such as "no-referrer" or "same-origin".	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Not implemented
	14.4.7	1	346	Verify that the content of a web application cannot be embedded in a third-party site by default and that embedding of the exact resources is only allowed where necessary by using suitable Content-Security-Policy: frame-ancestors and X-Frame-Options response headers.	Valid	DEVELOPMENT AND TEST STAGES	NONE	YES	NO	Done by specifying Header always set X-Frame-Options DENY in SSL File for HTTP Header contents for Apache. Set to nosniff so that it is not present on front end
Validate HTTP Request Header Requirements	14.5.1	1	749	Verify that the application server only accepts the HTTP methods in use by the application/API, including pre-flight OPTIONS, and logs/alerts on any requests that are not valid for the application context.	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Not implemented
	14.5.2	1	346	Verify that the supplied Origin header is not used for authentication or access control decisions, as the Origin header can easily be changed by an attacker.	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Not implemented
	14.5.3	1	346	Verify that the Cross-Origin Resource Sharing (CORS) Access-Control-Allow-Origin header uses a strict allow list of trusted domains and subdomains to match against and does not support the "null" origin.	Non-valid	DEVELOPMENT AND TEST STAGES	NONE	NO	NO	Not implemented
	14.5.4	2	306	Verify that HTTP headers added by a trusted proxy or SSO devices, such as a bearer token, are authenticated by the application.	Not Applicable	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY	DOES NOT APPLY

&A

Page &P