text stringlengths 9 408 |
|---|
[1301.20 --> 1301.92] or maybe they did |
[1301.92 --> 1302.64] and then they wiped it |
[1302.64 --> 1303.44] so there's no track. |
[1303.52 --> 1304.14] So maybe they did |
[1304.14 --> 1305.08] do something nefarious. |
[1305.26 --> 1306.08] I have no idea. |
[1306.08 --> 1306.50] I mean, |
[1306.52 --> 1307.04] if your password |
[1307.04 --> 1307.56] is 22, |
[1307.80 --> 1310.22] maybe old Alex |
[1310.22 --> 1311.14] didn't know how to check. |
[1313.06 --> 1313.42] Yeah. |
[1313.52 --> 1313.72] I mean, |
[1313.74 --> 1314.36] back in the day, |
[1314.50 --> 1316.54] that was something |
[1316.54 --> 1317.90] you just didn't really think of |
[1317.90 --> 1318.74] way back in the day. |
[1318.82 --> 1319.32] Things were just |
[1319.32 --> 1319.92] on the internet. |
[1320.10 --> 1322.14] When I first got exposure |
[1322.14 --> 1324.12] to TCP IP networking, |
[1324.68 --> 1325.82] everything had a public |
[1325.82 --> 1326.56] internet address |
[1326.56 --> 1327.32] on the network. |
[1327.72 --> 1328.84] And it wasn't until |
[1328.84 --> 1330.18] sometime later |
[1330.18 --> 1331.36] that we had firewalls |
[1331.36 --> 1332.12] and NATs. |
[1332.20 --> 1333.04] And so for a short period |
[1333.04 --> 1333.30] of time, |
[1333.34 --> 1333.90] you could basically |
[1333.90 --> 1334.80] connect to everything. |
[1336.30 --> 1337.58] There was some crazy stuff |
[1337.58 --> 1338.32] we did back then. |
[1338.88 --> 1339.58] I didn't want to put you guys |
[1339.58 --> 1339.98] on the spot, |
[1340.08 --> 1341.00] but I would be curious |
[1341.00 --> 1343.14] about how to go about |
[1343.14 --> 1344.30] detecting some of this stuff, |
[1344.54 --> 1344.76] you know, |
[1344.78 --> 1345.62] even from a most |
[1345.62 --> 1347.00] very basic level. |
[1347.68 --> 1348.00] Hmm. |
[1348.18 --> 1348.42] Well, |
[1348.48 --> 1348.82] I mean, |
[1348.82 --> 1349.24] I'm sure Alex, |
[1349.26 --> 1350.10] you probably have a few ideas. |
[1350.26 --> 1351.18] My first couple |
[1351.18 --> 1351.78] that come to mind |
[1351.78 --> 1353.40] would be know what processes |
[1353.40 --> 1353.94] should be writing |
[1353.94 --> 1354.58] on your box, |
[1354.72 --> 1355.60] check your logs. |
[1355.96 --> 1356.46] I mean, |
[1356.48 --> 1358.16] almost every single time |
[1358.16 --> 1359.70] that a client machine |
[1359.70 --> 1360.10] or something |
[1360.10 --> 1361.56] was behaving poorly, |
[1362.24 --> 1363.18] I could almost immediately |
[1363.18 --> 1364.14] just suss it out |
[1364.14 --> 1364.84] by running top. |
[1365.10 --> 1365.54] I mean, |
[1365.58 --> 1365.90] really, |
[1366.18 --> 1366.40] because, |
[1366.54 --> 1366.64] you know, |
[1366.70 --> 1367.52] you know what that machine |
[1367.52 --> 1368.40] is supposed to be doing. |
[1368.60 --> 1369.58] And if there's some process |
[1369.58 --> 1370.50] going crazy on there |
[1370.50 --> 1371.34] that has nothing to do |
[1371.34 --> 1372.28] with the responsibilities |
[1372.28 --> 1373.18] of that box, |
[1373.28 --> 1374.38] you got a pretty good idea |
[1374.38 --> 1374.98] of what it is. |
[1375.66 --> 1376.56] And then you look |
[1376.56 --> 1377.18] at your logs, |
[1377.26 --> 1377.42] right? |
[1377.42 --> 1378.96] You look at the active users |
[1378.96 --> 1380.42] that are logged onto the system |
[1380.42 --> 1381.96] and you kind of start |
[1381.96 --> 1382.62] tracing it back. |
[1382.70 --> 1383.22] Usually you'll look |
[1383.22 --> 1383.80] at the process |
[1383.80 --> 1384.32] and there'll be like |
[1384.32 --> 1386.08] some weird path |
[1386.08 --> 1386.64] or URL |
[1386.64 --> 1387.86] for a process |
[1387.86 --> 1388.72] that looks normal, |
[1388.82 --> 1389.92] but it's in the wrong place |
[1389.92 --> 1390.68] or it's being run |
[1390.68 --> 1391.56] by the wrong user |
[1391.56 --> 1392.92] and you kind of track |
[1392.92 --> 1393.54] it back from there. |
[1394.40 --> 1395.44] Depends where |
[1395.44 --> 1396.98] your expertise lies. |
[1397.48 --> 1399.12] If you're a networking guy, |
[1399.38 --> 1400.24] you could use something |
[1400.24 --> 1401.32] like Snort, |
[1401.84 --> 1402.64] which is essentially |
[1402.64 --> 1404.52] a packet filter |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.