Mtu yeyote ambaye amejaribu kuendesha mashine pepe kwenye wingu anafahamu vyema kwamba bandari ya kawaida ya RDP, ikiwa itaachwa wazi, itashambuliwa mara moja na mawimbi ya majaribio ya nguvu ya nenosiri kutoka kwa anwani mbalimbali za IP duniani kote.
Katika makala hii nitaonyesha jinsi ya Unaweza kusanidi jibu la kiotomatiki kwa nguvu ya kikatili ya nenosiri kwa kuongeza sheria mpya kwenye ngome. Kuaminiana ni kwa kukusanya, kuchambua na kuhifadhi data ambayo haijaundwa, ambayo tayari ina mamia ya miitikio iliyoainishwa kwa aina mbalimbali za mashambulizi.
Katika Quest InTrust unaweza kusanidi vitendo vya majibu wakati sheria inapoanzishwa. Kutoka kwa wakala wa kukusanya kumbukumbu, InTrust hupokea ujumbe kuhusu jaribio lisilofanikiwa la uidhinishaji kwenye kituo cha kazi au seva. Ili kusanidi uongezaji wa anwani mpya za IP kwenye ngome, unahitaji kunakili sheria maalum iliyopo ya kugundua uidhinishaji mwingi ambao haujafaulu na ufungue nakala yake kwa uhariri:
Matukio katika kumbukumbu za Windows hutumia kitu kinachoitwa InsertionString. (huku ni kuingia kwa mfumo bila kufaulu) na utaona kuwa sehemu tunazovutiwa nazo zimehifadhiwa katika InsertionString14 (Jina la Kituo cha Kazi) na InsertionString20 (Anwani ya Mtandao ya Chanzo). Unaposhambulia kutoka kwa Mtandao, sehemu ya Jina la Workstation itawezekana zaidi. kuwa tupu, kwa hivyo mahali hapa ni muhimu kubadilisha thamani kutoka Anwani ya Chanzo ya Mtandao.
Hivi ndivyo maandishi ya tukio 4625 yanavyoonekana:
An account failed to log on.
Subject:
Security ID: S-1-5-21-1135140816-2109348461-2107143693-500
Account Name: ALebovsky
Account Domain: LOGISTICS
Logon ID: 0x2a88a
Logon Type: 2
Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: Paul
Account Domain: LOGISTICS
Failure Information:
Failure Reason: Account locked out.
Status: 0xc0000234
Sub Status: 0x0
Process Information:
Caller Process ID: 0x3f8
Caller Process Name: C:WindowsSystem32svchost.exe
Network Information:
Workstation Name: DCC1
Source Network Address: ::1
Source Port: 0
Detailed Authentication Information:
Logon Process: seclogo
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Zaidi ya hayo, tutaongeza thamani ya Anwani ya Chanzo ya Mtandao kwenye maandishi ya tukio.
Kisha unahitaji kuongeza script ambayo itazuia anwani ya IP katika Windows Firewall. Chini ni mfano ambao unaweza kutumika kwa hili.
Hati ya kusanidi ngome
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string]
$SourceAddress
)
$SourceAddress = $SourceAddress.Trim()
$ErrorActionPreference = 'Stop'
$ruleName = 'Quest-InTrust-Block-Failed-Logons'
$ruleDisplayName = 'Quest InTrust: Blocks IP addresses from failed logons'
function Get-BlockedIps {
(Get-NetFirewallRule -Name $ruleName -ErrorAction SilentlyContinue | get-netfirewalladdressfilter).RemoteAddress
}
$blockedIps = Get-BlockedIps
$allIps = [array]$SourceAddress + [array]$blockedIps | Select-Object -Unique | Sort-Object
if (Get-NetFirewallRule -Name $ruleName -ErrorAction SilentlyContinue) {
Set-NetFirewallRule -Name $ruleName -RemoteAddress $allIps
} else {
New-NetFirewallRule -Name $ruleName -DisplayName $ruleDisplayName -Direction Inbound -Action Block -RemoteAddress $allIps
}
Sasa unaweza kubadilisha jina la sheria na maelezo ili kuzuia mkanganyiko baadaye.
Sasa unahitaji kuongeza hati hii kama hatua ya kujibu sheria, washa sheria na uhakikishe kuwa sheria inayolingana imewashwa katika sera ya ufuatiliaji katika wakati halisi. Wakala lazima awashwe ili kuendesha hati ya majibu na lazima awe na kigezo sahihi kilichobainishwa.
Baada ya mipangilio kukamilika, idadi ya uidhinishaji ambao haukufanikiwa ilipungua kwa 80%. Faida? Nini kubwa!
Wakati mwingine ongezeko ndogo hutokea tena, lakini hii ni kutokana na kuibuka kwa vyanzo vipya vya mashambulizi. Kisha kila kitu huanza kupungua tena.
Kwa muda wa wiki ya kazi, anwani 66 za IP ziliongezwa kwa sheria ya firewall.
Ifuatayo ni jedwali lenye majina 10 ya watumiaji ya kawaida ambayo yalitumika kwa majaribio ya uidhinishaji.
username
Idadi
Kwa asilimia
msimamizi
1220235
40.78
admin
672109
22.46
user
219870
7.35
contoso
126088
4.21
contoso.com
73048
2.44
msimamizi
55319
1.85
server
39403
1.32
sgazlabdc01.contoso.com
32177
1.08
administrateur
32377
1.08
sgazlabdc01
31259
1.04
Tuambie kwenye maoni jinsi unavyojibu vitisho vya usalama wa habari. Je, unatumia mfumo gani na ni rahisi kiasi gani?
Ikiwa ungependa kuona InTrust ikifanya kazi, katika fomu ya maoni kwenye tovuti yetu au niandikie kwa ujumbe wa kibinafsi.
Soma nakala zetu zingine juu ya usalama wa habari:
(makala maarufu)
Chanzo: mapenzi.com