Skip to content

Instantly share code, notes, and snippets.

View cryptolopes's full-sized avatar

Nelson cryptolopes

  • Lisboa, Portugal
View GitHub Profile
find /var/lib/docker/containers/ -type f -name "*.log" -delete
@cryptolopes
cryptolopes / saft-ao-TaxCountryRegion.csv
Last active May 5, 2020 19:13 — forked from tadast/countries_codes_and_coordinates.csv
Countries with their (ISO 3166-1) Alpha-2 code, Alpha-3 code, UN M49, average latitude and longitude
País Código Alpha-2 Código Alpha-3 code Código Numérico Latitude (média) Longitude (média)
Afghanistan AF AFG 4 33 65
Albania AL ALB 8 41 20
Algeria DZ DZA 12 28 3
American Samoa AS ASM 16 -14.3333 -170
Andorra AD AND 20 42.5 1.6
Angola AO AGO 24 -12.5 18.5
Angola-Cabinda AO-CAB AGO 24 -5.57 12.20
Anguilla AI AIA 660 18.25 -63.1667
Antarctica AQ ATA 10 -90 0
@cryptolopes
cryptolopes / ETH_EuroToken_report.md
Created October 23, 2019 17:59 — forked from yuriy77k/ETH_EuroToken_report.md
Euro Token Audit Report.
@cryptolopes
cryptolopes / ETH_LoveAirCoffee_v2_report.md
Created October 23, 2019 17:59 — forked from yuriy77k/ETH_LoveAirCoffee_v2_report.md
LoveAirCoffee v2 audit report.
@cryptolopes
cryptolopes / ETH_Dai_report.md
Created October 23, 2019 17:58 — forked from yuriy77k/ETH_Dai_report.md
Dai Security Audit Report
@cryptolopes
cryptolopes / ADS-T1076.md
Created October 23, 2019 17:57 — forked from wesinator/ADS-T1076.md
Example alerting and detection strategy for RDP

Goal

Detect Remote Desktop Protocol (RDP) activity that could indicate malicious or unauthorised access.

Categorization

This activity is categorised as Lateral Movement / Remote Desktop Protocol in the killchain and ATT&CK frameworks respectively.

Strategy Abstract

The strategy consists of:

  • Collecting Windows authentication logs
  • Checking remote logon type events for unauthorised user access
@cryptolopes
cryptolopes / 16CA481.md
Created October 16, 2019 14:20 — forked from okeefj22/16CA481.md
CA481 - Software Quality

Question 1

Q1(a)

  • an error is a mistake made by a human which produces an incorrect result
  • a defect is the consequence of the human error in the code
  • a failure is the manifestation of the defect in the running software

Q1(b)

  • testing is carried out to discover defects in code
  • debugging is carried out to discover the cause of the defect

QA Test Planning Methodology

Planning

To begin the planning stage, QA's have to meet with developers and/or product owners and/or clients to discuss the documentation and project scope prior to implementation to begin the planning stage. Documentation comes in various forms, from paper to electronic, but no matter what kind, these product/project documents have to be analyzed. The time reading it should also be time dedicated to looking for any discrepancies and issues, meanwhile also building and spec'ing test dependancies, frameworks and cases. The product document is examined thoroughly for complexity, UI features, functionality, issues and most importantly requirements; some aspects may need to be changed to work. Analysis as a QA is feedback for the developers.

Implementation

Feedback to developers signals the beginning of the implementation stage. The product is placed into the warm and loving hands of development. During this stage QA's begin to build test cases for the upcoming product. T

@cryptolopes
cryptolopes / ValidateXmlFile.ps1
Last active June 11, 2020 00:27 — forked from DominicCronin/ValidateXmlFile.ps1
ValidateXmlFile: a powershell script for validating XML
function ValidateXmlFile {
param ([string]$xmlFile = $(read-host "Please specify the path to the Xml file"))
$xmlFile = resolve-path $xmlFile
"==============================================================="
"Validating $xmlFile using the schemas locations specified in it"
"==============================================================="
# The validating reader silently fails to catch any problems if the schema locations aren't set up properly
# So attempt to get to the right place....
Push-Location (Split-Path $xmlFile)