## Verwendung

Inquisitor hat fünf grundlegende Befehle, die `scan`, `status`, `classify`, `dump` und `visualize` umfassen.```
usage: inq [-h] {scan,status,classify,dump,visualize} ...

optional arguments:
  -h, --help            show this help message and exit

command:
  {scan,status,classify,dump,visualize}
                        The action to perform.
    scan                Search OSINT sources for intelligence based on known
                        assets belonging to the target.
    status              Prints out the current status of the specified
                        intelligence database.
    classify            Classifies an existing asset as either belonging or
                        not belonging to the target. Adds a new asset with the
                        specified classification if none is present.
    dump                Dumps the contents of the database into a JSON file
    visualize           Create a D3.js visualization based on the contents of
                        the specified intelligence database.

### Status

Im Statusmodus gibt das Tool einfach eine kurze Zusammenfassung des Status Ihrer Scandatenbank aus.```
usage: inq status [-h] [-s] DATABASE

positional arguments:
  DATABASE      The path to the intelligence database to use. If specified
                file does not exist, a new one will be created.

optional arguments:
  -h, --help    show this help message and exit
  -s, --strong  Indicates if the status will be based on the strong ownership
                classification.

### Dump

Im Dump-Modus können Sie die Inhalte der Intelligence-Datenbank in eine menschenlesbare JSON-Datei exportieren.```
usage: inq dump [-h] [-j FILE] [-a] DATABASE

positional arguments:
  DATABASE              The path to the intelligence database to use. If
                        specified file does not exist, a new one will be
                        created.

optional arguments:
  -h, --help            show this help message and exit
  -j FILE, --json FILE  The path to dump the JSON file to. Overwrites existing
                        files.
  -a, --all             Include rejected assets in dump.

## Arbeitsablauf

Jetzt, da Sie die grundlegenden Funktionen von Inquisitor kennen, ist es an der Zeit zu lernen, wie man es *tatsächlich* verwendet. Inquisitor wurde mit den folgenden Schritten entwickelt:

### Seeding (Initialbefüllung)

In diesem Schritt enthält Ihre Intelligence Database noch nichts. Wir müssen irgendwo anfangen, also befüllen Sie die Datenbank mit Assets, von denen Sie wissen, dass sie zu Ihrer Zielorganisation gehören. Dies können Sie mit dem Befehl `classify` tun.

### Scannen

Jetzt, da die Datenbank Assets enthält, die bekanntermaßen zu Ihrer Zielorganisation gehören. Sie können dann mit dem Scannen fortfahren. Dies können Sie mit dem Befehl `scan` tun.

Wenn Sie den Befehl `scan` in Ihrer Intelligence Database aufrufen, führt Inquisitor die `transform`-Methoden von Assets aus, die als `accepted` klassifiziert sind. Sobald das Scannen abgeschlossen ist, erhalten Sie möglicherweise weitere Assets, die potenziell zu Ihrer Zielorganisation gehören.

Wenn Sie keine neuen Assets erhalten, können Sie entweder Ihre Intelligence Database mit neuen Informationen befüllen oder einfach zum Abschluss des Prozesses übergehen, indem Sie zum Schritt 'Berichterstattung' gelangen.

### Klassifizieren

Während Inquisitor für Sie eine automatische Asset-Klassifizierung durchführt, könnte es einige Assets übersehen, die tatsächlich zu Ihrer Zielorganisation gehören.

Wenn dies geschieht, müssen Sie den Datenbankinhalt überprüfen und die Assets manuell klassifizieren. In der Regel sollten Sie besonders auf **Registrant**-Assets achten, da es keine Möglichkeit gibt, die Eigentümerschaft für diesen Asset-Typ automatisch zu bestimmen. Außerdem sind die meisten anderen Asset-Typen auf die Eigentümer-Klassifizierung von Registrant-Assets angewiesen, um zu bestimmen, ob sie zu Ihrem Ziel gehören oder nicht, daher ist es definitiv am besten, auf Ihre Registrant-Assets zu achten. Außerdem haben Sie von vornherein nicht viele Registrant-Assets, daher ist es nicht so schwer, sie zu durchsuchen.

### Berichterstattung

Sie können eine Visualisierung der Assets, die zu Ihrer Zielorganisation gehören, mit dem Befehl `visualize` oder dem Befehl `dump` erstellen.

## Demo

Ich habe Videodemonstrationen des Tools unter folgendem Link: https://drive.google.com/open?id=0B_O70BVu38TRclo5dWRBWkdTTWc

Ich konnte den Lauf des Befehls `scan` jedoch nicht vollständig aufzeichnen, da mein kostenloser Bildschirmrekorder nur bis zu 10 Minuten aufzeichnet.

## Entwicklung

Das Inquisitor-Projekt ist wie folgt aufgebaut:```
.
|-- README.md
|-- inquisitor
|   |-- __init__.py
|   |-- assets
|   |   |-- __init__.py
|   |   |-- block.py
|   |   |-- email.py
|   |   |-- host.py
|   |   |-- linkedin.py
|   |   `-- registrant.py
|   |-- extractors
|   |   |-- __init__.py
|   |   `-- emails.py
|   `-- sources
|       |-- __init__.py
|       |-- google_search.py
|       `-- shodan_search.py
|-- inq
|-- report
|   `-- index.html
|-- setup.py
`-- tests
    |-- __init__.py
    `-- test_inq.py

Retrieves the primary key and asset object for the asset with the provided 
type and identifier.

asset_type: class, required

    The type of the asset to retrieve from the Intelligence Database. You
    will actually have to pass the class object of the asset type you want
    to retrieve.

identifier: any, required

    The identifier of the asset to retrieve. Consider the identifier as the
    unique attribute of an asset object. As for which attribute is to be
    used to identify an asset, it depends on the contents of the OBJECT_ID
    variable in the asset module.

create: bool, optional, default=False

    When no matching asset object is found, a new one will be created and 
    returned if this parameter is set to True. The new asset will not
    necessarily be stored in the Intelligence Database unless specified
    using the "store" parameter. However, I suggest you do not do this as
    adding assets to the Intelligence Database is the responsibility of
    another module.

store: bool, optional, default=False

    When a new asset is created when none is found, the new one will be
    stored in the Intelligence Database. As said previously, I suggest that
    you do not do this as adding assets to the Intelligence Database is the
    responsibility of another module.

A two-element tuple where the first element is the database primary key of 
the element returned, and the second element is the deserialized asset 
object retrieved from the database.

None if the asset was not found.

If the asset was not found and the create flag was set to True, the primary
key member of the tuple will be set to None.

### Assets

Um einen neuen Asset-Typ zu erstellen, erstellen Sie eine neue Datei im Verzeichnis `inquisitor/assets` und fügen Sie den folgenden Skelettcode ein:```python
import inquisitor.assets

class ASSET_NAMEValidateException(Exception):
    pass

def canonicalize(ASSET_IDENTIFIER):
    return ASSET_IDENTIFIER

def main_classify_args(parser):
    parser.add_argument(
        '-aASSET_NAME_LETTER', '--accept-ASSET_NAME',
        metavar='ASSET_NAME',
        type=canonicalize,
        nargs='+',
        help='Specifies a ASSET_NAME to classify as accepted.',
        dest='ASSET_NAMEs_accepted',
        default=list(),
    )
    parser.add_argument(
        '-uASSET_NAME_LETTER', '--unmark-ASSET_NAME',
        metavar='ASSET_NAME',
        type=canonicalize,
        nargs='+',
        help='Specifies a ASSET_NAME to classify as unmarked.',
        dest='ASSET_NAMEs_unmarked',
        default=list(),
    )
    parser.add_argument(
        '-rASSET_NAME_LETTER', '--reject-ASSET_NAME',
        metavar='ASSET_NAME',
        type=canonicalize,
        nargs='+',
        help='Specifies a ASSET_NAME to classify as rejected.',
        dest='ASSET_NAME_rejected',
        default=list(),
    )

def main_classify_canonicalize(args):
    accepted = set(args.ASSET_NAMEs_accepted)
    unmarked = set(args.ASSET_NAMEs_unmarked)
    rejected = set(args.ASSET_NAME_rejected)
    redundant = set.intersection(accepted, unmarked, rejected)
    if redundant:
        raise ValueError(
            ('Conflicting classifications for ASSET_NAMEs '
            ': {}').format(list(redundant))
        )
    accepted = set([canonicalize(a) for a in accepted])
    unmarked = set([canonicalize(a) for a in unmarked])
    rejected = set([canonicalize(a) for a in rejected])
    return (accepted, unmarked, rejected)

class ASSET_NAME(inquisitor.assets.Asset):

    def __init__(self, ASSET_IDENTIFIER, owned=None):
        super(self.__class__, self).__init__(owned=owned)
        self.ASSET_IDENTIFIER = canonicalize(ASSET_IDENTIFIER)
        # TODO: Perform other initialization actions here

    def __eq__(self, other):
        if not isinstance(other, self.__class__):
            return False
        return self.ASSET_IDENTIFIER == other.ASSET_IDENTIFIER

    def related(self, repo):
        # Prepare the results
        results = set()
        # TODO: Create related assets here based on the attributes of this asset
        # Return the results
        return results

    def transform(self, repo, sources):
        # Prepare the results
        assets = set()
        # Google Transforms
        if sources.get('google'):
            subassets = self.cache_transform_get('google', repo)
            if not subassets:
                # Acquire API
                google = sources['google']
                # TODO: Perform Google queries here and the results to 'subassets'
                # Cache The Transform
                self.cache_transform_store('google', subassets)
            assets.update(subassets)
        # Shodan Transforms
        if sources.get('shodan'):
            subassets = self.cache_transform_get('shodan', repo)
            if not subassets:
                # Acquire API
                shodan = sources['shodan']
                # TODO: Perform Google queries here and the results to 'subassets'
                # Cache The Transform
                self.cache_transform_store('shodan', subassets)
            assets.update(subassets)
        # Return the results
        return assets

    def is_owned(self, repo):
        if self.owned:
            return True
        # TODO: Automatically determine ownership based on repo contents
        return False

    def parent_asset(self, repo):
        # TODO: Return parent asset based on repo contents
        return None

REPOSITORY = 'ASSET_REPOSITORY'
ASSET_CLASS = ASSET_NAME
OBJECT_ID = 'ASSET_IDENTIFIER'

related

  Returns the set of assets directly related to the asset in question (i.e.
  those that can be derived without querying a search engine).

  When creating asset objects, make sure you use the 
  IntelligenceRepository.get_asset_string method instead of instatiating a 
  new one your self so the asset can be returned from the repository if it 
  exists.

  Set the create flag to True when calling the method in question in order
  to return a new object when one isn't found.

  Set the store flag to False as appending assets is the job of another
  module.

repo: IntelligenceRepository

    The Intelligence Repository that is being used in the current context.

Set of assets directly related to the asset in question. 

Stellen Sie sicher, dass Sie diese Gelegenheit nicht verpassen, etwas Farbe in Ihre```
Function

    transform

Description
  
      Returns the set of assets potentially related to the asset in question
      (i.e. those that can be derived by querying a search engine).

      You may access search engine objects through the provided sources
      parameter.

      Each search engine object has a transform method which automatically
      creates asset objects for you. You just need to provide it the repository
      and your query string, and then append the objects it returns to the set
      of assets to be returned by your asset's transform method.

Parameters

    repo: IntelligenceRepository

        The Intelligence Repository that is being used in the current context.

    sources: dict

        The list of search engine objects that are available for use.

Returns

    Set of assets potentially related to the asset in question.
    

pip install twikit

pip install twikit[all]

import asyncio
from twikit import Client

USERNAME = 'your-username'
EMAIL = 'email'
PASSWORD = 'password'

# Initialize client
client = Client('en-US')

async def main():
    # Login to Twitter
    await client.login(
        auth_info_1=USERNAME,
        auth_info_2=EMAIL,
        password=PASSWORD
    )

    # Get user information
    user = await client.get_user_by_screen_name('MyTwitter')
    print(f"User ID: {user.id}, Followers: {user.followers_count}")

    # Get user's tweets
    user_tweets = await user.get_tweets('Tweets')
    for tweet in user_tweets:
        print(f"Tweet ID: {tweet.id}, Text: {tweet.text}")

asyncio.run(main())

import asyncio
from twikit import Client

async def main():
    client = Client('en-US')

    # Get trending topics
    trends = await client.get_trends('trending')
    for trend in trends:
        print(f"Trending: {trend}")

    # Search tweets with concurrent rate limiting
    # Max 10 concurrent operations, 2-second delay between batches
    tweets = await client.search_tweet(
        'query', 'Top',
        concurrent=True, max_concurrent=10, delay=2
    )

is_owned

 Determines if there is high confidence that this asset does indeed belong
 to the target. Usually checks for any "strong" classification tag first by
 looking at the contents of the "owned" variable, before performing
 automatic evaluation.

 Automatic evaluation depends on what type of asset you're writing. For
 example, for a Host asset, the secondary sources of determining ownership
 would include looking if its registrant is owned by the target, if it's
 parent domain is owned by the target. etc.

repo: IntelligenceRepository

    The Intelligence Repository that is being used in the current context.

True it is determined with high confidence that this asset does indeed 
belong to the target.

EINGABE:```
Function

    parent_asset

Description
  
     Returns the asset object that is considered the parent of this asset
     object.

Parameters

    repo: IntelligenceRepository

Returns

    The asset object that this asset falls under (e.g. a Block is under a 
    Registrant, a Host is under a Block, a Host is under another Host, an Email
    is under a Host, etc. This is primarily used for visualization.