Skip to content

Instantly share code, notes, and snippets.

Both Bitbucket and GitHub provide various features and integrations for code review, but they do not have built-in plugins or pipelines specifically designed for code plagiarism review. However, there are third-party tools and services that can be integrated with Bitbucket or GitHub to perform code plagiarism checks.

Here are some options for code plagiarism review:

  1. Code similarity detection tools: There are several code similarity detection tools available that can be integrated with Bitbucket or GitHub. These tools analyze the code and compare it against a large database of existing code to identify similarities. Some popular code similarity detection tools include Moss, JPlag, and Plagiarism Checker X.

  2. Continuous Integration (CI) pipelines: You can set up CI pipelines in Bitbucket or GitHub to automatically run code plagiarism checks as part of the code review process. CI tools like Jenkins, Travis CI, or CircleCI can be configured to execute code plagiarism detection scripts or tools dur

@johnfelipe
johnfelipe / temp3.md
Created March 11, 2024 15:59
preview table RCA
Section Total UHES Generic SAESA RCA
Total Documents 8 7 1
Step 1: Define the problem
- Identify the team 6 6 0
- Clearly state the problem 6 6 0
- Understand the problem 6 6 0
- Define S.M.A.R.T. objectives 4 4 0
Step 2: Contain the problem 6 6 0
Step 3: Root Cause Analysis (RCA) - Establish Root Cause (or causes)
@johnfelipe
johnfelipe / temp2.md
Created March 8, 2024 21:37
Reporte de Exploración de Pentesting - HCL AppScan Standard-Invicti Professional Edition-Acunetix Premium

Reporte de Exploración de Pentesting

Como Senior Security Engineer, he realizado una exploración exhaustiva de pentesting utilizando tres herramientas líderes en el mercado: HCL AppScan Standard, Invicti Professional Edition y Acunetix Premium. A continuación, presento un análisis detallado de cada herramienta, seguido de comparativos entre ellas.

Comparativo entre Herramientas de Pentesting

Característica HCL AppScan Standard Invicti Professional Edition Acunetix Premium
Tipo de Pruebas Dinámicas y estáticas Dinámicas y estáticas Dinámicas
Facilidad de Uso Interfaz intuitiva Interfaz amigable Interfaz altamente intuitiva

Informe de exploración de PENTESTING

Fecha: 04 de enero de 2024

Ubicación: Medellín, Antioquia, Colombia

Ingenieros de seguridad: Jhon FelipeUrrego Mejia

Herramientas utilizadas:

1
00:00:00,660 --> 00:00:06,860
what's going on guys welcome back today we're doing a bit of challenge with
2
00:00:06,860 --> 00:00:11,860
Splunk so the room name is investigating with Splunk and we're given a scenario
3
00:00:11,860 --> 00:00:18,100
1
00:00:00,660 --> 00:00:06,860
qué está pasando chicos, bienvenidos de vuelta hoy estamos haciendo un desafío
con Splunk, así que el nombre de la sala es investigando con Splunk y se nos
presenta un escenario en el que debemos responder a las preguntas en un intento
de analizar qué sucedió y cuáles fueron las razones o los artefactos clave de la
violación de seguridad. Según la descripción, el analista SOC Johnny ha
observado algunos comportamientos anómalos en los registros de algunas máquinas
con Windows. Entonces ahí es donde ocurrió el incidente. En una estación de
trabajo con Windows. Parece que el adversario tiene acceso a algunas de estas
{
"dataSources": {
"ds_7N1LKEOc": {
"type": "ds.search",
"options": {
"queryParameters": {
"earliest": "0",
"latest": ""
},
"query": "| inputlookup security_example_data.csv \n| where network_type!=\"visitor_office\" AND (device_type=\"$device_type$\") \n| iplocation network_ip \n| geostats latfield=lat longfield=lon count by network_type \n| eval employee_office=employee_office*123 \n| eval contingent_office=contingent_office*123 \n| eval employee_remote=employee_remote*123 \n| eval contingent_remote=contingent_remote*123 \n| eval visitor_office=visitor_office*15"
{
"dataSources": {
"ds_7N1LKEOc": {
"type": "ds.search",
"options": {
"queryParameters": {
"earliest": "0",
"latest": ""
},
"query": "| inputlookup security_example_data.csv \n| where network_type!=\"\" \n| iplocation network_ip\n| geostats latfield=lat longfield=lon count by network_type\n| eval employee_office=employee_office*123\n| eval contingent_office=contingent_office*123\n| eval employee_remote=employee_remote*123\n| eval contingent_remote=contingent_remote*123\n| eval visitor_office=visitor_office*15"
{
"dataSources": {
"ds_search_1": {
"type": "ds.search",
"options": {
"query": "| inputlookup firewall_example.csv \n| search host=host8 OR host=host18\n| eval host=case(host=\"host8\", \"spend\", host=\"host18\", \"score\", 1=1, host)\n| eval myTime=strftime(timestamp,\"%H:%M\") \n| chart count over myTime by host\n| eval score=score*2\n| eval spend=spend*1500\n| fields myTime spend score\n| rename score as \"Security Score\", spend as \"Security Spend\"",
"queryParameters": {
"earliest": "-24h@h",
"latest": "now"
}
Using cached GitPython-3.1.40-py3-none-any.whl (190 kB)
Collecting cachetools<6,>=4.0
Using cached cachetools-5.3.2-py3-none-any.whl (9.3 kB)
Collecting altair<6,>=4.0
Using cached altair-5.2.0-py3-none-any.whl (996 kB)
Collecting protobuf<5,>=3.20
Using cached protobuf-4.25.1-cp37-abi3-manylinux2014_x86_64.whl (294 kB)
Collecting click<9,>=7.0
Using cached click-8.1.7-py3-none-any.whl (97 kB)
Collecting toml<2,>=0.10.1