DevOps by REBRAIN
Открытые практикумы по DevOps, Linux, Golang, Networks, Security Мы на связи: info@rebrainme.com +7 (499) 116-34-68 https://rebrainme.com/ Зарегистрированы в РКН: https://knd.gov.ru/license?id=674db558d793bc0b0b8845ff®istryType=bloggersPermission
Show more📈 Analytical overview of Telegram channel DevOps by REBRAIN
Channel DevOps by REBRAIN (@rebrain_devops) in the Russian language segment is an active participant. Currently, the community unites 28 754 subscribers, ranking 4 619 in the Technologies & Applications category and 22 378 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 28 754 subscribers.
According to the latest data from 31 October, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -98 over the last 30 days and by 0 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 8.12%. Within the first 24 hours after publication, content typically collects 6.53% reactions from the total number of subscribers.
- Post reach: On average, each post receives 2 335 views. Within the first day, a publication typically gains 1 878 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 10.
- Thematic interests: Content is focused on key topics such as dovecot, linux, скрипт, postfix, yandex.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“Открытые практикумы по DevOps, Linux, Golang, Networks, Security
Мы на связи:
info@rebrainme.com
+7 (499) 116-34-68
https://rebrainme.com/
Зарегистрированы в РКН: https://knd.gov.ru/license?id=674db558d793bc0b0b8845ff®istryType=bloggersPermiss...”
Thanks to the high frequency of updates (latest data received on 01 November, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
variables:
# Пример переменной для сканирования образа
IMAGE: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
TEST_URL: "http://app-test:8080"
stages:
- sast
- dast
- report
# 1. Анализ зависимостей, IaC и контейнера (Trivy)
trivy-scan:
stage: sast
image: aquasec/trivy:latest
script:
- trivy fs --format json --output trivy.json .
- trivy image --severity CRITICAL --format json --output trivy-image.json $IMAGE
artifacts:
when: always
paths:
- trivy.json
- trivy-image.json
# 2. Динамическое тестирование (OWASP ZAP Baseline)
zap-scan:
stage: dast
image:
name: owasp/zap2docker-stable
entrypoint: [""] # Сброс entrypoint обязателен для запуска скриптов в GitLab
script:
# Заменили full-scan на baseline, чтобы не блокировать MR на часы
- zap-baseline.py -t $TEST_URL -r zap_report.html -x zap_alerts.xml
allow_failure: true # DAST часто находит минорные баги, не стопарим весь пайплайн
artifacts:
when: always
paths:
- zap_report.html
- zap_alerts.xml
# 3. Агрегация в DefectDojo (единое окно)
defectdojo-upload:
stage: report
image: curlimages/curl:latest
script:
# Загрузка результатов Trivy
- >
curl -X POST "https://dojo.company.com/api/v2/import-scan/"
-H "Authorization: Token $DOJO_API_KEY"
-F "product_name=MyApp"
-F "engagement_name=CI-CD"
-F "scan_type=Trivy Scan"
-F "file=@trivy.json"
# Загрузка результатов ZAP
- >
curl -X POST "https://dojo.company.com/api/v2/import-scan/"
-H "Authorization: Token $DOJO_API_KEY"
-F "product_name=MyApp"
-F "engagement_name=CI-CD"
-F "scan_type=ZAP Scan"
-F "file=@zap_alerts.xml"
Что вы получите:
✅ SAST/SCA на каждом MR
✅ DAST на тестовом стенде
✅ Все уязвимости в одном месте (DefectDojo)
Это базовая конфигурация. Завтра расскажем про новый модуль, в котором будет все подробно разобрано)