# nmap\_stuff\_-\_recon

NMAP STUFF - RECON Recon: Looking for

On the system:

LPAR names / IP addresses User name convention - for brute forcing CICS regions application names passwords config files user guides

Mailing lists (these are public)

IBMMAIN IBMTCP-L CICS-L RACF-L

Googlehacking

site:share.confex.com

sharpoint: LPAR - CICS - IMS attachmate: 'CICS Explorer' 'TSO ID'

\============================================

NMAP/Scanning

Nmap is good at identification I.E. - knowing it's a mainframe

## Safe scan for mainframe

nmap -n -p- -dd -oA ip.date.initial 

nmap -sV -p 23,22,21 -vv -d -oA ip.date.service 

Enumerate the LU - Enumerate any VTAM applications

Available Nmap scripts

tn3270-screen vtam-enum cics-enum tso-enum tso-brute cics-user-enum cics-user-brute cics-info

nmap --script tn3270-screen --script-args tn3270-screen.commands="tso;user;password"

nmap -n -p 23  -sV -vv --script vtam-enum --script-args vtam-enum.path=/home/test,idlist=vtam.list


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://0xdecaf2bad.gitbook.io/red-team-notes/93-mainframe/nmap_stuff_-_recon.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.