Security Framework. In addition to your obligations set forth in the Security Schedule, you expressly agree to establish, implement and update, as necessary, security policies, procedures, and systems related to the initiation, processing and storage of ACH Origination entries.
Security Framework. The required security framework is provided for in the SECURE ERDS software. The ERDS software shall use a minimum of 128 bit file and image encryption. Industry standard Secure Sockets Layer (SSL) and user login with password that is encrypted shall be employed. User passwords are controlled by the user and at a minimum changed at 90 day intervals to reduce security exposure.
a) Endpoint Security (Authentication Token)
Security Framework. Security framework uses an ACL architecture similar to Windows NT. An access control entry allows or denies a player or a group access to game capabilities in service resolution. The set of actions for player in a game include sending and receiving messages and accessing service data such as the collection of current players. The security token is a 32bit value in which every bit represents an allowed action. A security token is associated with a player-game or a group-game pair to form an Access Control Entry (ACE). The collection of all ACEs for a game forms the service's Access Control List (ACL).
Security Framework. Encryption will be a minimum 128bit file and image encryption. Secure Socket Layer (SSL) and user loginlpassword will be employed. User passwords are controlled by the Submitter and should be monitoredlor changed periodically to ensure security. Computers on which documents originate must have all critical operating system patches applied, must have a firewall (hardware or software) installed, and must have up to date virus scan software.
Security Framework. The required security framework is provided for in the SECURE G2G Portal software. The SECURE G2G Portal software shall use a minimum of 128-bit file and image encryption. Industry standard Secure Sockets Layer (SSL) and user login with password that is encrypted shall be employed. User passwords are controlled by the State Government Agency and at a minimum changed at 90-day intervals to reduce security exposure.
1. ACES will create electronic files containing lien data in an XML format as required by SECURE comprised of an image of the lien notice document and associated index information to include the following data elements: ▪ Taxpayer Legal Business Name ▪ Taxpayer Legal Individual Name ▪ Address ▪ Lien ID ▪ External Code
2. ACES will use the following URLs for uploading files: ▪ For testing: xxxxx://xxxxx.xxx.xxxxxx-xxxxxxxxx.xxx ▪ For production: xxxxx://xxxxx.xxxxxx-xxxxxxxxx.xxx
3. ACES will successfully test all functionality for the exchange of electronic lien filings prior to submitting the initial production file.
4. The XML electronic files sent to SECURE shall not contain PII, including social security numbers, driver’s license numbers and/or date of birth.
5. ACES will notify SECURE of Notice of State Lien form changes impacting the images included in the electronic files prior to including the revised forms in production files.
Security Framework. We implement internal security controls that align with the NIST Cybersecurity Framework v1.
Security Framework. The required security framework is provided for in the SECURE G2G Portal software. The SECURE G2G Portal software shall use a minimum of 128 bit file and image encryption. Industry standard Secure Sockets Layer (SSL) and user login with password that is encrypted shall be employed. User passwords are controlled by the Government Agency and at a minimum changed at 90 day intervals to reduce security exposure.
a) Endpoint Security (Authentication Token) - Government Agencies will require one token for each agency staff member that will be utilizing the UI. For use of the token to submit documents through the SECURE G2G Portal for recording electronically, please refer to the SECURE G2G Portal User Manual.
Security Framework. 2.1 Moorepay has in place structured Security and Compliance Teams. The areas covered by the Security & Compliance teams are: Compliance and Standards; Data Privacy and Protection; Legal and Regulatory compliance matters; Business Continuity and Disaster Recovery; Security Management; Physical Security; and Vendor Security and Compliance Management.
2.2 Moorepay has an Information Security Management System (ISMS) which is aligned with the international standards and code of practice ISO 27002. Security controls are based on industry best practice and aligned with ISO 27001 and SSAE18. Moorepay has achieved certification to the ISO 27001:2013 standard.
Security Framework. The Contractor shall comply with either of the following:
Security Framework. The Kentucky Online Gateway (KOG) provides user provisioning and authorization services. Every component of QHI including MEMS shall invoke KOG services prior to executing a user request from within the MEMS solution. The new MEMS solution shall utilize the KOG solution for user provisioning and authorization services.
