DHS Law Enforcement Information Sharing Service

# DHS Law Enforcement Information Sharing Service **Aliases:** LEIS; LEISS; Law Enforcement Information Sharing Service **Entity class:** Legal, policy, or governance instrument **Domain:** Austin Research / Surveillance **Doc Type:** Research entity **Source basis:** Supplied essay and the specifically identified records; verification scope is recorded in [[wiki/Austin Surveillance Evidence Ledger|the evidence ledger]]. The **DHS Law Enforcement Information Sharing (LEIS) Service** is the federal interface that makes NCTCOG’s LEAP materially more than a regional records cache. The DHS briefing by Special Agent James W. Buckley Jr. describes a web service joining state and local systems to DHS person-centered case information exposed through [[wiki/ICEPIC|ICEPIC]]. It supplies an identified technical interface, an identified federal information source, and an identified agreement layer. ## The decisive partner slide Slide 15 places **“LEAP (NCTCOG)” under existing MOUs**, beside [[wiki/ARJIS|ARJIS]], LInX Northwest, [[wiki/OneDOJ|OneDOJ]], AzLINK’s Tucson node, the Los Angeles Sheriff’s Department, [[wiki/Texas Data Exchange|TDEx]], and National Capital Region LInX. The following lines describe **NLETS and N-DEx agreements as expected in FY2010**, while slide 16 separately lists negotiations still in discussion. These are three different agreement states. The copy inspected is an agency-authored presentation hosted by Public Intelligence. It has no visible presentation date; its FY2010 planning language supplies historical context, not an exact MOU signature date. The slide is documentary evidence of DHS’s reported agreement with the regional LEAP system. The underlying signed MOU and its technical annex remain distinct retrieval targets. ## What passed through the interface Slides 4–6 describe service-oriented web exchange using GJXDM/NIEM models and LEXS formats, with message transformation into a universal format. Slides 8–11 describe shareable TECS and ENFORCE person records: initial biographical matches, then more detailed identifiers and contextual fields. This is a person-query interface through existing local systems, rather than a requirement that every officer operate a standalone federal application. The same briefing restricts the described exposure to non-sensitive records, identifies sensitive categories, and places additional record types in a future expansion. It therefore supports **federally interfaced criminal-justice access**, not unlimited access to every DHS holding. Co-listing establishes each named system’s reported relationship to DHS; it leaves direct exchange between every pair of partners unresolved. ## The layers behind a query The source document makes the architecture clearer when its components are kept separate: - [[wiki/Treasury Enforcement Communications System|TECS]] and the [[wiki/Enforcement Integrated Database|Enforcement Integrated Database]] supplied operational person records; - [[wiki/ICEPIC|ICEPIC]] supplied historical [[wiki/Identity and Relationship Analysis|identity and relationship analysis]] and repository functions; - [[wiki/National Information Exchange Model|NIEM]] and [[wiki/Law Enforcement Exchange Specification|LEXS]] supplied common representations for exchange; and - [[wiki/IBM DataPower|DataPower]] transformed and routed messages between partner and backend formats. After ICEPIC and [[wiki/DHS Pattern and Information Collaboration Sharing System|DPICS2]] were retired, LEIS continued as a standalone service drawing selected information from source systems including [[wiki/Investigative Case Management|ICM]]. This is a change from repository-centered analysis to service-mediated access. It does not establish that every ICEPIC analytic capability survived unchanged. This makes LEIS the documented successor to the **exchange function**, while [[wiki/FALCON Search and Analysis|FALCON-SA]], [[wiki/Palantir Gotham|Gotham]], [[wiki/Investigative Case Management|ICM]], and the newer [[wiki/Case Management and Analytics Platform|CMAP]] carry the principal case-management and analytical functions. The distinction is developed in [[research/ICEPIC Successor Stack - Distributed Case Management Analytics and Information Sharing|ICEPIC Successor Stack]]. The detailed historical response could contain a credit-card number as an identifier. It did not thereby expose a universal card-transaction ledger. [[wiki/Financial Transaction Data|Transaction histories]] and [[wiki/Bank Secrecy Act|BSA]] information belong to separate financial-system and legal-access layers. ## Austin’s entry path Austin’s September 27, 2012 authorization and its NCTCOG agreement identify the local entry point into this arrangement. The contract names federal agency units among potential LEAP participants. The relevant route is **Austin participation agreement → NCTCOG LEAP → DHS LEIS/ICEPIC interface**. The federal agreement resides at the regional-system layer, so a separate city–DHS signature is not the instrument used to create this particular route. [[wiki/Interlocal Information Sharing|Interlocal Information Sharing]] develops that institutional mechanism. [[wiki/IC ITE|IC ITE]] supplies a comparison with enterprise identity, policy, and shared services; the LEIS evidence itself concerns the criminal-justice sharing environment. ## Connected entries [[wiki/Law Enforcement Analysis Portal|Law Enforcement Analysis Portal]] · [[wiki/North Central Texas Council of Governments|North Central Texas Council of Governments]] · [[wiki/ICEPIC|ICEPIC]] · [[wiki/Treasury Enforcement Communications System|TECS]] · [[wiki/Enforcement Integrated Database|EID]] · [[wiki/Investigative Case Management|ICM]] · [[wiki/National Information Exchange Model|NIEM]] · [[wiki/Law Enforcement Exchange Specification|LEXS]] · [[wiki/IBM DataPower|IBM DataPower]] · [[wiki/ARJIS|ARJIS]] · [[wiki/LInX|LInX]] · [[wiki/OneDOJ|OneDOJ]] · [[wiki/Texas Data Exchange|Texas Data Exchange]] · [[wiki/National Data Exchange|National Data Exchange]] · [[wiki/Nlets|Nlets]] · [[wiki/Interlocal Information Sharing|Interlocal Information Sharing]] · [[wiki/Semantic Interoperability|Semantic Interoperability]] ## Sources and corpus context - [[research/The Austin Surveillance Field|The Austin Surveillance Field]] - [DHS — Law Enforcement Information Sharing Service briefing, slides 4–16; existing MOUs on slide 15](https://info.publicintelligence.net/DHS-LEISS.pdf) - [City of Austin — LEAP interlocal agreement, recitals and §§2–7](https://services.austintexas.gov/edims/document.cfm?id=176641) - [Austin — approved minutes, September 27, 2012, p. 8, items 57–58](https://services.austintexas.gov/edims/document.cfm?id=177584) **Cluster:** [[wiki/Austin Surveillance Field|Austin Surveillance Field]] · [[wiki/Austin Executable Loop|Austin Executable Loop]] · [[wiki/Austin Surveillance Evidence Ledger|Austin Surveillance Evidence Ledger]] ## Relationships  This entry's documented connections are expressed in its definition and related-work routes, with provenance retained in the source-linked material.